Is there a way I can build all cljs files in foo/*.cljs to an output-dir of bar/*.js? From reading the guide it looks like I have to explicitly specify every file/namespace symbol?

@alex395 Perhaps using :modules / code splitting? E.g. for nbb I have:

{:deps {:aliases [:test]}
 :builds {:modules {:js-options {:keep-as-import #{"fs" "module" "path"
                                                   "react" "react-dom"}}
                    :compiler-options {:infer-externs :auto}
                    :target :esm
                    :runtime :node
                    :output-dir "out"
                    :modules
                    {:nbb_core {:init-fn nbb.core/init}
                     :nbb_main {:init-fn nbb.main/main
                                :depends-on #{:nbb_core}}
                     :nbb_reagent {:init-fn nbb.reagent/init
                                   :depends-on #{:nbb_core}}
                     :nbb_promesa {:init-fn nbb.promesa/init
                                   :depends-on #{:nbb_core}}}
                    :build-hooks [(shadow.cljs.build-report/hook
                                   {:output-to "report.html"})]}
          :test {:target :node-test
                 :ns-regexp "-test$"
                 :output-to "target/test/test.cjs"
                 :autorun true}}}

and this outputs a nbb_reagent.js file and a nbb_promesa.js file

but you have to specify the modules

I want to infer them from the files that exist in a given pathe

write a script to generate the module configuration?

Yeah... I was trying to avoid that 😄 I guess its fine though

but if you specify the main namespace of each directory which depends on the rest in that directory and nothing else depends on it, then it should work out with only specifying that one

Hmm, just to be clear on what I'm trying to do, I have a nextjs project which transforms .js files that each have a default export function which gets turned into a lambda, and I want to write those .js files in cljs. So in my head I have a set of cljs/*.cljs files, and shadow will generate pages/api/*.js files for me, perhaps its not worth it and I should just learn javascript properly though...

I saw this build hook which is maybe an approach I can use, though it hardcodes the export (I guess thats fine though?) https://github.com/thheller/next-cljs/blob/master/src/main/shadow/next_js.clje

I guess the dream is for netlify/vercel etc to add support for bb/nbb 😄

I am trying to use a library that apparently has a dependency of js-dom - I get 88 errors with shadow-cljs as follows: node_modules/jsdom/lib/jsdom/living/generated/AbortSignal.js:13 constructor is missing a call to super() Has anyone run into this ? Or know of a fix?

@tbrooke I have a library that depends on js-dom and it's successfully working with shadow-cljs, currently at version 16.4.0 of js-dom. What's the version there?

@chris358 Thank I checked and it was using 15.2.1 - trouble is that it ie buried in a slew of dependencies - I’ll try to upgrade it or get it upgraded

If it says ^15.2.1 then you should be able to npm i js-dom@latest at the top level and it will use the updated version instead.

I'm not sure if that will help though.

Hey everyone, I’m learning Clojure(Script). Been doing a cljs frontend using jacekschae shadow-cljs-tailwindcss boilerplate https://github.com/jacekschae/shadow-cljs-tailwindcss. I’m confused on how to deploy it to heroku :thinking_face: On one hand package.json already contains the release script and I get everything I need to serve it inside the public folder. But in this case I’d serve a node.js app. On the other hand I think it would be more clean to create a jar and use heroku java buildpack. I can’t find any beginner resource that explains this clearly. Can someone provide some hints? TIA. ❤️

not v familiar with heroku, but i would imagine that if you don't have a backend that heroku has a way of deploying a static site

I would look into that