hey! where I can find :id-of-build which is needed to connect to cljs build? Described like here: https://github.com/thheller/shadow-cljs/wiki/Cider

your :builds {:id-of-build ...}. :app or so.

yeap, it worked, thank you!

I've noticed that upon first use, shadow-cljs downloads maven deps and stores them in ~/.m2 - is there a way of configuring this location?

not currently no

That's a shame, it's making CI builds more painful than they need to be

hmm thats a standard maven thing so I'd expect there to be solutions for this with CI

dunno if I can make configurable

Are you delegating to lein/mvn or doing it yourself?

currently using https://github.com/cemerick/pomegranate which is the same lein is using. might switch to tools.deps in the future.

https://github.com/cemerick/pomegranate/blob/master/src/main/clojure/cemerick/pomegranate/aether.clj#L328

looks like its configurable though

OK, I'll give that a go

try setting :local-repo "wherever" in your shadow-cljs.edn config

yup

need to delete .shadow-cljs/classpath.edn though

that currently does not account for :local-repo changing

ofc

Working correctly, thanks

@thheller in clojurescript I recall you have to tag functions with ^:export to avoid the names being re-written by advanced compilation, however I see no mention of that with shadow (for the :node-module target). What’s the behaviour?

not required, the compiler knows what it needs to know due to the :main config

Also, can I benefit from dead code elimination with :node-module or simialr by specifying a namespace containing my “API”, and get everything that the API doesn’t depend on to be eliminated by Closure?

for :npm-module everything you don't ^:export is fair game and will most likely be removed

ah

I don’t quite get the difference between :node-library and :node-module then

I think

I’ll re-read the doc

:node-library generates ONE file object with exports. so you end up with ONE require("the-thing")

:npm-module leaves the namespaces intact so you can require individual namespaces require("the-thing/some.ns")

@thheller so that’s similar to using :node-module and writing a special namespace myself, e.g. “api”, which contains my functions?

:node-library generates a single file mapping to various functions in various namespaces?

with :node-library you specify the :exports in the config. they can be from different namespaces yes.

but with :node-module, as you said, I need to mark any function that I wish to use post-compilation with ^:export, right?

yes

ok. Thank you! 🙂

Do you have a recommended way to integrate shadow with other js projects? e.g. would you generate a npm package and symlink it from your other projects?

Or else?

I tried various approaches yesterday night

Just curious if you have one in mind

specifically to get live-reload to work nicely with create-react-app/parcel/webpack/else

ideally you let shadow-cljs compile the JS completely

integrating the other way around is always going to be lossy

in particular live-reload .. that pretty much goes out the window if you let anything else bundle the code

I did this test a while ago. https://github.com/thheller/react-redux-realworld-example-app/tree/this-is-madness

basically took the entire create-react-app project. moved some things around but didn't change one line of code.

and use shadow-cljs to compile it some some extra help from babel

but thats nowhere near reliable enough now .. but thats the direction I was going with

integration with webpack is easy enough and really depends on how your JS project is setup

you could create a dummy npm package for the JS output

or just output it into some directory and refer to the files directly via either relative paths

or webpack resolve config help

I didn’t realise shadow could bundle javascript as well

interesting

and could i mix cljs, cljc and js sources this way?

yes

https://github.com/thheller/shadow-cljs-examples/tree/master/local-js/src/demo

Basically I am working on a project for which the “core” is written in clojurescript, but I want to develop the interface with React in JS

app.cljs uses foo.js which uses bar.cljs

full interop

unfortunately all of this is not totally finished yet since you need to run babel manually currently

is this kind of “mixed” project documented?

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

I’ll try to replicate the example though 🙂

very experimental

While I am at it: you mentioned using the REPL only through your editor. If I wish to use a REPL through the command line, and have the ability to reload namespaces that changed on the fly, how could I do it?

Right now my project is set up with boot. Most of the project is composed of cljc files

I use the Clojure (not clojurescript) REPL, and wrote a function to reload namespaces (that I call manually, (reload); it looks for files that changed and reloads the namespaces)

rlwrap npx shadow-cljs clj-repl (reload)

oh there is a built-in reload function?

ah you meant I should expose mine

sorry

yeah, which goes back to my question on loading a namespace by default when starting the repl

but I can figure that out

shadow-cljs really isn't meant for Clojure though

if you want reload for CLJS I recommend using the build-in reload stuff

I wouldn’t mind using the clojurescript repl

so long as I can get stuff auto-reloaded

or manually reloaded somehow

which REPL though? if you let webpack process your sources the REPL and live-reload pretty much don't work

that would just be to debug the “core”, which is entirely written in clojurescript

so shadow-cljs browser-repl or so?

it’s basically a library of functions

(require 'some.ns :reload) should do it then

@thheller have been watching your commits. Slow compiles where always my biggest pet peeve with big project cljs builds! DX just got much more pleasant. 💯 thanks for the performance tweaks!

I think there is still lots of tuning that could be done. just need time to do it 🙂

on hot code update: renaming a namespace seems to give shadow-cljs some problems. It complains that it can’t find the namespace anymore