Is nbb using shadow-cljs under the hood at all for dependency management? I spent wayy too long debugging an issue without any success trying to use shadow-cljs to create a node script that basically just :require'd an esm module and called it directly. nbb was the right tool for the job anyways but if they are using shadow-cljs I'd be interested to learn how nbb manages esm modules so seamlessly in case I need to use shadow-cljs for something other than node scripting in the future
@emma.griffin When you are using nbb, you're not using shadow-cljs. It's only compiled during development using shadow-cljs but then after that, shadow-cljs is no longer involged. With dependency, do you mean a JS dependency or CLJS dependency?
JS dependency
but huge shoutout to how easy nbb is, thank you for your hard work
Thank you! :) nbb just uses dynamic import for this.
In shadow-cljs you can more or less get the same with :target :esm
I tried that without any success
if you have an example project doing it I'd love to see though!
It's documented here: https://github.com/babashka/nbb?tab=readme-ov-file#migrating-to-shadow-cljs
that gist may be a little out of date
but shadow's docs about :target :esm should be the thing to look for.
but if you're just writing a script, that's what nbb is for :)