shadow-cljs

shaunlebron 2025-12-12T10:43:48.104199Z

looks like cljs 1.12.134 is being used on master, but not published yet, would you mind publishing? trying to fix the Vector warnings, thanks

thheller 2025-12-13T07:19:17.331099Z

I fixed those before? you still getting them?

👍 1
shaunlebron 2025-12-15T21:50:51.899409Z

thanks, 3.3.4 fixed it

cjohansen 2025-12-12T12:38:27.224819Z

Is there some way I can override the name of the shadow-cljs.edn file? To switch between different configs

thheller 2025-12-13T07:18:53.996579Z

why would you want that? isn't two different builds enough?

thheller 2025-12-13T07:18:59.660459Z

and no, there is not currently

cjohansen 2025-12-13T07:41:51.912379Z

To be able to use different sets of deps aliases. We have some dev tooling that we want to ensure doesn't somehow end up in the production build.

thheller 2025-12-13T07:42:57.080859Z

then just use the aliases directly via clj

thheller 2025-12-13T07:43:17.354249Z

shadow-cljs release app is identical to clj -A:whatever -M -m shadow.cljs.devtools.cli release app

thheller 2025-12-13T07:43:41.848369Z

you aren't bound to only ever using the aliases defined via :deps in shadow-cljs.edn, when using clj directly the :deps setting is ignored entirely.

thheller 2025-12-13T07:44:16.193539Z

but generally shadow-cljs is designed in a way that creeping dev dependencies into a release build should not happen

thheller 2025-12-13T07:44:51.660469Z

build reports lets you verify this easily https://shadow-cljs.github.io/docs/UsersGuide.html#build-report

cjohansen 2025-12-13T07:47:55.293059Z

Cool, thanks 👍