that is not supported and also not necessary, just enable all aliases you need always. deps.edn does not control what the build ends up using, so extra dependencies hurt no one

https://code.thheller.com/blog/shadow-cljs/2018/02/08/problem-solved-source-paths.html

ok I see. Now I understand that what I actually need is to build a node binary (executable). I'm a bit confused between node-library and npm-module

I want to build a project, publish it to npm, and then in another project install it and execute as a binary (I guess it has to be via yarn or npm and not deps.edn, since I don't want to build it again)

sounds like you want :node-script?

I recommend creating a dedicated packages/the-thing folder with its own package.json

then you make :node-script build with :output-to "packages/the-thing/index.js"

then you npm publish in the packages/the-thing folder

and others can npm install the-thing

you can add a "bin" entry in package.json so others can run npx the-thing foo bar to execute

ok ill try that, thanks again

thats more or less how you get the shadow-cljs command, see https://github.com/thheller/shadow-cljs/tree/master/packages/shadow-cljs

What should be in the npm package when I publish? At first I thought only out and bin, but then I received the error

/home/app/dev/deps/apps/drift-v2/node_modules/@deps/deps-ops/.shadow-cljs/builds/main/dev/out/cljs-runtime/goog.debug.error.js

thats why I suggested to use the packages/the-thing folder. Only what is in that you need

not the cljs source files, not shadow-cljs, not .shadow-cljs, nothing else

and only publish npx shadow-cljs release ... builds, not the development versions

https://www.npmjs.com/package/shadow-cljs?activeTab=code

see how that only has the cli/dist.js file generated by shadow-cljs and the manually written helper files, nothing else

👍