@bhauman, not sure if you’re aware of this, but a big way to improve things if anyone is using windows and wsl2 is to specifically store the project in the ubuntu side and edit/load/write everything from there. Things massively improved after I did that. It appears that there’s a fairly hefty penalty associated with not doing so and it’s a really easy thing to do. For example file listeners can subtly break, edits take forever to propagate, etc. Not sure if you want to document this? Happy to give additional details =)…
Oh sorry, I'm running IntelliJ in WSL2, well the integrated terminal and directly loading my project off of the WSL2 file-system. Which seems to make everything work... I was surprised by how much of a difference it made!
@folcon I just wrote a blog about Clojure and WSL2 here: https://blog.michielborkent.nl/2020/07/26/remote-wsl2-clojure/ So far it's been going great.
Sweet, will take a look thanks =)…
Not sure how you have been doing things before. You ran Java from Windows natively and some other stuff within WSL2?
Well I’ve swapped most things to running wsl2 directly, so terminal etc works there, but I use intellij for dev, so the default repl actually uses the windows jvm… If I want a ubuntu jvm I just run a terminal and use it from there… It’s an odd little setup, but it does allow me to test my code is cross platform…
It would be cool if IntelliJ had support for WSL2 right, like Visual Studio supposedly has
I liked the starting directory tip btw, didn’t know you could do that =)…
I think you can also edit your files on WSL via this network share thing
//wsl$.... If you start your REPL in WSL2 you could try to connect to it from IntelliJ and run things all in WSL2, but edit in IntelliJ possibly
or get crazy and run IntelliJ in WSL2 and run an X server in Windows 🙂
That’s basically what I’ve been doing, it works really well =)…
I very frequently get this and I am not sure what to do to correct it. It sometimes corrects itself when I delete the generated files when spinning up Figwheel Main from VScode. But at the moment I keep getting it. My project files are what exist when you have completed Create a Build in the figwheel docs.
@grounded_sage what version of figwheel and clojurescript are you using?
I think you are using an old version of figwheel with a new version of ClojureScript
Okay. It was following the tutorial. Went from some cljs work I was doing on a larger project to not even being able to run that. Like some caching bug was happening. I also had issues on the larger project where it seemed the libraries that had an old version of figwheel etc were somehow hijacking the dev page made by figwheel main.
@grounded_sage so you followed the current tutorial? and you got these problems? So you are using figwheel 0.2.11 and clojurescript 1.10.773 ?
hmmm libraries that reference figwheel.main?
the reason I ask is because the figwheel.core.provided? function doesn’t exist in the current version of figwheel and it’s incompatible with the newer clojurescript
I must apologise. I am away from computer now so I can’t really provide much value to the conversation at present. Will screenshot so I don’t lose these questions and will try get back to you tomorrow.