@thheller I ran into the error I talked before, that I have to delete .shadow-cljs to make it works again. I have the error stack, I'm not sure whether it will help or not, the build target is node-script.

god damn slack. where is the download button for this?

Click the three dots, then View file details?

just wanted to download a .txt file or something 😛

guess I'll copy and paste

I'll upload a file

emmmm...

thx

hmm yeah can't make much of that either. dunno why it would be looking for something $cljs.

this is actually node right?

Yes, it's node.

and just restarting shadow-cljs was not enough?

yes, restarting is not enough. I'm sure the process is stopped

when it happens, there will be some random compile error, usually occurs to somewhere unchanged

that usually points to 2 shadow-cljs versions running competing with each other

oh, two versions of shadow-cljs?

well not versions. instances. like launching shadow-cljs twice in the same project

you mean in the same project?

both compiling at the same time and overwriting each others files

the "instance" is the one I start with npx shadow-cljs ... ?

or some internal process?

don't know how you are running things

npx shadow-cljs watch app and emacs cider jack-in or something

two separate jvm instances created somehow

I guess just twice npx shadow-cljs watch app would cause this two if executed fast enough. meaning before one becomes "ready" and thus the second thinking it was first and starting as normal

I use cider, and cider use npx shadow-cljs server. But I don't think I started it twice.

Oh

will it matter if I have a test build?

only if that instance also starts compiling the app build as well

I typically recommend running npx shadow-cljs server manually yourself

and then use cider connect instead of the jack-in stuff

but I don't use cider so no clue if that is actually possible 😛

For the code files required in both builds(app, test). There will be only 1 version of cache in .shadow-cljs?

Okay, since more information is required. Probably I can figure how to reproduce for the next time.

😎

there will be one .shadow-cljs/builds/app/... and one .shadow-cljs/builds/test/...

but if you have two processes compiling the app build they will both write to .shadow-cljs/builds/app/...

there is only supposed to be one process compiling a build not two

got it

the next time this happens don't do anything. leave everything running. type jps. that should list all running java processes

you can get further details on what these processes actually are via jinfo <pid> from jps

or use something like jvisualvm. listing all jvm processses. or just ps I guess if you are on a mac/linux

okay

I'll confirm whether there are more than one shadow instance

BTW, is there a change log for shadow-cljs?

https://github.com/thheller/shadow-cljs/blob/master/CHANGELOG.md

❤️