If anyone upgraded cider I made .dir-locals.el file with this code:

((nil . ((projectile-project-type . lein-test)
         (eval . (progn
                   (require 'cider)
                   (add-to-list 'cider-cljs-repl-types '("Shadow CLJS" "(do (shadow.cljs.devtools.server/start!) (shadow.cljs.devtools.api/watch :app) (shadow.cljs.devtools.api/nrepl-select :app))" nil))
                   (setq projectile-create-missing-test-files t))))))

@mitchelkuijpers it still requires lein right?

Yes for this solution you need leiningen

Or you could connect to nrepl which shadow-cljs starts but then you have to add their middleware first

getting rid of lein would be neat since I have more control over the setup then

I'd love to get it working with absolutely zero-conf

We want to move to a deps.edn setup at one point so that would be nice. Not sure how that works though. I am talking in the #cider room about this

Btw we don't need leiningen but we need to inject the nrepl middleware

the cider middleware is automatically added when its on the classpath

hi, has anyone tried packaging shadow-cljs compiled JS (production) code into jars, for consumption in another cljs projects?

@fbielejec for CLJS you should only be packaging the cljs source files never compiled code

but shadow-cljs currently does not provide anything to do the packaging of those

I see - and what about publishing as a module to npm registry, and then requiring via node_modules?

either :node-library or :node-script work for that. see https://shadow-cljs.github.io/docs/UsersGuide.html#target-node-library

:npm-module also works

shadow-cljs started out as :node-script but :npm-module is slight more flexible but also more complex

publish is just npm publish

Gotcha - I'm looking into ways of utilizing shadow-cljs compiled modules in upstream projects still using :cljsbuild. I suppose one could force fetching of that dependency via :npm-deps or lein-npm plugin, :notify or some other mechanism?

I cannot emphasize this enough. DO NOT USE compiled CLJS code in OTHER cljs projects

you will get into a horrible mess if you try to do this

nothing will work at all

problem is that the compiled version of the library will contain its own version of cljs.core

which will conflict with the other CLJS code being compiled in the project

so you can't pass a cljs map from the project code to the library

there is no viable option if the other project is using cljsbuild and doesn't understand npm-deps properly

publishing to npm is only useful if you want your code to be consumable from JS

for CLJS the problem is that the cljs compiler needs access to the sources. there really isn't anything that can be done about this.

thanks - this will save my time from going down that rabbit hole 🙂

@thheller I decided to just publish the p5.tiledmap to npm -- I got it working too.

http://take.ms/rVr5f

cool!