@potetm definitely might be a bug, I’ve never tested that flow myself either

I’m assuming that for :npm-deps, if you want the default behavior in the next release (indexing externally-supplied node_modules) you should specify :npm-deps {} and, in particular :npm-deps true is not legit. (There are unit tests like this, so this mode appears to work.) If we want the legal values to be boolean? and map? I can update https://github.com/clojure/clojurescript-site/pull/264

yes let’s expand that

Done https://github.com/clojure/clojurescript-site/pull/264/files and https://github.com/clojure/clojurescript-site/pull/244/commits/570b560bd35300010d322afd891524c4c55aa682

thanks!

@dnolen I found a race condition in the CLJS compiler which you "accidentally" fixed recently via a perf opt. Not sure if its worth considering fixing this differently. See https://dev.clojure.org/jira/browse/CLJS-2922?focusedCommentId=50319&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-50319