Fork me on GitHub
#shadow-cljs
<
2019-06-29
>
pez14:06:50

@thheller can I wish for the .nrepl-port file to be created even if [:nrepl :port] is set? Calva uses this file’s creation as a signal in its jack-in process (because limitations in the vscode API:s).

mauricio.szabo14:06:22

Is there a way to ask for Shadow to not try to resolve a JS dependency, and just maps to a specific require? The reason for that is that while developing an atom package I found out that I can compile it with :js-provider :shadow to avoid using node_modules. This made the package smaller, installs faster, and when Atom starts the package adds waaay less time on startup time

mauricio.szabo14:06:13

But as the target is as node library, sometimes dependencies tries to require('fs') for example, and shadow's compilation complains that it can't find the module for it

thheller15:06:26

@pez .shadow-cljs/nrepl.port is always generated?

mauricio.szabo19:06:35

Just... Wow! Thanks a lot, it works perfectly!

pez15:06:31

@thheller , alright, I'll run a few more tests with it, maybe I jumped to the conclusion. (Probably did.)

thheller15:06:41

just remember to use the correct file. .nrepl-port is wrong and kind of unreliable since it doesn't want to interfere with lein creating one

pez15:06:24

Ah, maybe that's what happening. So I should be looking in the .shadow-cljs dir instead? Calva doesn't treat shadow special with this file today, but maybe it should.

thheller15:06:06

yes, always use the .shadow-cljs/*.port files

pez15:06:23

Roger that. I'll need to look closer at jack-in for shadow web projects anyway, I noticed today.

pez15:06:20

Another thing, while I am at this. When using the nrepl op for loading a file. With figwheel (both flavors) i get a result back. But not with shadow. This puzzles me a bit. What could be causing that?

pez15:06:11

(The result is from the last form in the file.)

thheller15:06:42

its possible the result isn't sent

pez15:06:20

I'll look closer at which messages I get. Maybe there is something else I can use to signal that the operation has been carried out.

roooor18:06:34

Hi guys, just getting started with clojure and im trying to run a basic project on my windows machine. When I run watch it runs the project for a minute or two and then exits

roooor18:06:47

heres a screen shot of the process

roooor18:06:39

tried to add

:fs-watch {:watcher :polling}
to shadow-cljs.edn but that didn't alleviate the issue

mauricio.szabo19:06:35

Just... Wow! Thanks a lot, it works perfectly!

thheller20:06:47

@qwazilla I'm developing on windows myself and I can assure you that windows does not require any special settings

thheller20:06:05

I don't know why it would exit like that

thheller20:06:19

do you connect to the process in any way (REPL via your editor or so) or does it just exit after the first build?