@thheller thanks. I thought it was something on my end 🙂

@thheller I have :autorun true, The watcher recompiles the test target and I can run it using node, but it is not automatically run, AFACS.

:server-tests {:target :node-test
                         :output-to "target/test/tests.js"
                         :ns-regexp ".test."
                         :autorun "true"}

^ works for me

^ have a similar setup and it works for me as well

does anyone have an example using karma with devcards?

I seem to remember an example floating around

Does anyone know why the Shadow User Guide suggests an npm install of shadow-cljs both locally and globally?

https://shadow-cljs.github.io/docs/UsersGuide.html#_standalone_via_code_npm_code

> $ npm install --save-dev shadow-cljs > $ npm install -g shadow-cljs

I think the reason is because the global version installs the cli on your path but the local version is the actual compiler that gets used. you presumably want the compiler version checked into your source code control but it is convenient to have the cli on the path.

@nick828 the global install is just for convenience. only the one in the project actually matters

@lee.justin.m @thheller Thanks :thumbsup:

hmm, has anyone bumped into shadow-cljs - command completed without status #js { .. giant js object }?

i can only reproduce it in a ci environment, not locally. this probably means it has something to do with running inside a docker container. it’s kind of hard to debug becuase the output is something like {:status nil, :signal "SIGKILL", :output #js [nil nil nil], :pid 546, :stdout nil, :stderr nil … not super helpful 😞

after some more investigation, this seems like a memory issue. if i increase my docker limits (docker for mac) to 8gb instead of 4, my local docker image build completes. since i’m using circleci (which has a 4gb-per-build limit) i’m not really sure what else to do. oh no.