This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-19
Channels
- # announcements (19)
- # asami (9)
- # babashka (26)
- # beginners (87)
- # biff (23)
- # calva (6)
- # clerk (7)
- # clj-kondo (3)
- # cljsrn (3)
- # clojure (115)
- # clojure-belgium (1)
- # clojure-berlin (1)
- # clojure-europe (31)
- # clojure-gamedev (5)
- # clojure-nl (2)
- # clojure-norway (8)
- # clojure-uk (2)
- # clojurescript (43)
- # clr (23)
- # datalevin (1)
- # datomic (14)
- # dev-tooling (23)
- # fulcro (38)
- # graphql (1)
- # gratitude (1)
- # jobs (1)
- # lsp (30)
- # off-topic (7)
- # pathom (25)
- # portal (21)
- # quil (6)
- # releases (5)
- # remote-jobs (1)
- # shadow-cljs (34)
- # sql (5)
- # tools-deps (6)
- # xtdb (13)
Hello I am starting to take a look at using portal. Currently I am running my repl outside of vscode and connecting to it. When I run
portal.api.open { :vs-code :launcher }
I get an error where it cannot find the vs-code.edn file. I do have the vscode portal plugin installed. What might I be missing?good question, I launched code from a term but i can't recall what folder i was in at the time since I just have a workspace in vscode. Repl is launced in the actual project folder
https://github.com/djblue/portal/blob/master/src/portal/extensions/vs_code.cljs#L122-L129 is the code responsible for setting everything up, not sure why there is nothing in the .portal folder :thinking_face:
so same result but i did see a error popup on vscode "terminal process failed to launch .portal does not exist"
not sure what else. On latest versions, Fedora Linux OS. Launching the repl from a terminal and connecting to it via calva
I can test on linux when I get some time later, last I checked it worked but it doesn't hurt to try 👌
> There is .portal folder but nothing in it
That's the problem. There needs to be a vs-code.edn
file in the .portal directory. For some reason the 'vscode portal plugin/extension' did not write the file. As a workaround you could always put it in manually, with this contents (port is randomly generated):
{:host "localhost", :port 34771}
I'm also on Linux (pop!_os) and I think have noticed a similar problem. But it fixed itself: I uninstalled the extension then pressed the 'Restart Required' (or similar wording) button then found the extension again and then installed it again. By fixed I meant the folder and the file both appeared.