Fork me on GitHub
#shadow-cljs
<
2020-02-14
>
robert-stuttaford14:02:57

is there a way to watch a release build? debugging advanced-comp issues

robert-stuttaford14:02:52

i guess by putting :optimizations  `:advanced` on the dev build

teodorlu15:02:33

Would using an external tool like entr work for you?

find src | entr shadow-cljs ...
http://entrproject.org

teodorlu15:02:37

That way you don't expose yourself to any differences in behavior between running a "normal invocation" and a "partial reload" of sorts

martinklepsch17:02:34

After nuking node_modules to test some stuff I’m stuck with some shadow-cljs - failed to load errors. package.json and package-lock.json are the same so I’m a little confused what could be causing this.

thheller18:02:38

what kind of failed to load? there is some weird behavior if you delete too many node_modules files while a watch is running. it may not fully recover from that an may require a resatrt

martinklepsch18:02:56

module$node_modules$$firebase$firestore$dist$index_cjs
components.home.js TypeError: client.util.adapt_class is not a function
client.util.js TypeError: firebase.INTERNAL.registerComponent is not a function

martinklepsch18:02:15

I did restart the build multiple times

thheller18:02:58

@robert-stuttaford :optimizations does not apply to watch builds as it always forces :none. for debugging I suggest running shadow-cljs server and then shadow-cljs release app --pseudo-names or --debug whenever you make a change

👌 4
thheller18:02:18

that way you get reasonable fast feedback without waiting for shadow-cljs startup

robert-stuttaford18:02:34

thank you, i'll do that

Derek18:02:46

git ls-files | entr shadow-cljs release app --psuedo-names

robert-stuttaford18:02:52

it ended up being pretty fast without server anyway 😂

Derek18:02:53

might work for you with a server running