Fork me on GitHub
#shadow-cljs
<
2018-06-30
>
richiardiandrea00:06:27

when I deploy my Azure app, I get a bunch of:

Stack: Error: ENOENT: no such file or directory, open 'D:\home\arichiardi\git\laputa\lambda-cqrs\.shadow-cljs\builds\az\dev\out\cljs-runtime\goog.debug.error.js'
what am I missing?

richiardiandrea03:06:33

it looks like some path is built by looking at .shadow-cljs. This is shadow-cljs compile and I though I could still deploy that even if "unoptimized" without .shadow-cljs. Probably not - meaning compile is not self contained

mjmeintjes05:06:21

How do I build a local copy of shadow-cljs to test changes to the Clojure code?

mjmeintjes05:06:34

And how to I make my project use that local copy?

thheller09:06:43

@richiardiandrea if you deploy you MUST use shadow-cljs release your-thing. not compile.

thheller09:06:55

compile is a dev build only meant to run on the machine it was compiled one

👍 4
thheller09:06:16

@mjmeintjes option a) clone and lein install. option b) add <clone>/src/main to you :source-paths. option c) use lein + checkouts. option d) use deps.edn :local/root

thheller09:06:49

the bug you reported is due to a change I did in the resolve code to fix a different bug. guess I introduced more than I fixed. will take care of it in a bit

mjmeintjes21:06:42

@thheller Thanks, that seems pretty easy.

dpsutton22:06:17

I'm trying to crank up shadow-cljs and running into this. Anyone encountered this before?

dpsutton22:06:29

so it was missing javafx. and java-atk after that. 🦆