The directory structure looks like this • scripts/index.js • functions/node_modules • shadow-cljs.edn

well yeah the output should be functions/index.js

I assume this is node in which case node resolve rules apply

remember that node build targets by default do not bundle their dependencies. so they need to be available at runtime using node resolve rules. in short that is <script-dir>/node_modules and <script-dir>/../node_modules and so on going up

if you want a fully self contained script that has no outside dependencies I recommend post processing with https://github.com/vercel/ncc

shadow-cljs can bundle deps too but all of it is optimized for the browser so ncc generally works better for node builds

but in general I would just recommend putting the :output-to into the dir that also has the node_modules dir

gotcha, yeah that makes sense then. I’ll try to just move the file into functions . I did play with ncc at some point which also worked pretty well but not really required in this case.

I somehow thought that the :js-package-dirs option would magically tell the compiled script where to find packages but I think it’s slightly different / only has that effect for browser builds

yeah it only telle shadow-cljs where to find packages when bundling (which node targets don't do by default)

cool, it’s still used for node though is it? like for compile time warnings or stuff like that?

only for cases where you do (:require [react]) or any kind of symbol where shadow-cljs needs to verify you mean a npm package

but no it never looks at actual JS sources from node_modules for node builds

can't look at stuff like fs and so on anyways given they are built-in