i wonder if my shadow version is somehow ancient...

nope its fairly recent 2.19.4.

i would also be fine creating a release build another way, maybe i should just use the clojure shadow library directly?

can you explain your intent? pom is a task by the shadow-cljs cli command, which you do not use? however you can ask clj to generate a pom file for you, since it is in charge of generating the classpath? -Spom I believe?

I don't get what creating a pom has to do with creating a release build though?

help, info are all things provided by the shadow-cljs command, which runs in node and doesn't execute java for those

release watch compile are all done by the clojure parts

note that you can just continue using the shadow-cljs command? it'll just call clj for you. you only lose features by going with clj

@U05224H0W thanks thheller. I'm following the instructions as outlined here in the user guide. https://shadow-cljs.github.io/docs/UsersGuide.html#deps-edn > Example shadow-cljs.edn with :cljs alias >

{:deps {:aliases [:cljs]}
>  :builds ...}

{:paths [...]
>  :deps {...}
>  :aliases
>  {:cljs
>   {:extra-deps {thheller/shadow-cljs {:mvn/version <latest>}}}}

{:paths [...]
>  :deps {...}
>  :aliases
>  {:shadow-cljs
>   {:extra-deps {thheller/shadow-cljs {:mvn/version <latest>}}
>    :main-opts ["-m" "shadow.cljs.devtools.cli"]}}}
> clj -A:shadow-cljs watch app

clj -A:shadow-cljs pom

clj -A:shadow-cljs watch app

clj -A:shadow-cljs release app

shadow-cljs release app
shadow-cljs - config: /home/drewverlee/Centriq/centriq-web/frontend/shadow-cljs.edn
shadow-cljs - starting via "clojure"
Execution error (FileNotFoundException) at clojure.main/main (main.java:40).
Could not locate shadow/cljs/devtools/cli__init.class, shadow/cljs/devtools/cli.clj or shadow/cljs/devtools/cli.cljc on classpath.

Full report at:
/tmp/clojure-5691110849954872601.edn

Yea, if i add shadow-cljs as a dep (not behind an alias) to my deps.edn then i can run shadow-cljs release

you add :deps {:aliases [:cljs]} to shadow-cljs.edn

and add the thheller/shadow-cljs dependency to your deps.edn :cljs alias (or :shadow-cljs, or whatever alias you want)

you do NOT add the main opts

those you only add if you do NOT use the shadow-cljs command

if you do not use the shadow-cljs command I think you must use clj -M:shadow-cljs release app?

package.json is not relevant in this stage

> My best guess this is because shadow doesn't know about binaryage/devtools because it's a hidden behind a deps.edn aliase as an extra dep.

I don't follow

create one alias for CLJS and use that

or is your intent really to run everything via clj and no longer use the shadow-cljs command

the setups are different. what do you want?

i'm running some different combinations to see if i can answer my own question...

I understand now, the shadow-cljs.edn :deps :aliases are picked up when you run shadow-cljs at the command line, and so the deps.edn aliases by the same name as the one i gave shadow-cljs.edn shouldn't have a main-opt that calls out to shadow command line as well. That makes sense.

@U05224H0W For my own education, i wrote up a short explanation of how i understand the topic now that i have had a chance to review it. If you like, i can try to clean it up more and and it could be used in the docs, or not 🙂 The following is pulled from a markdown file, so the formatting is a tad off: # 3.2.2. integration with deps.edn and clj tool Shadow can pull dependencies from deps.edn and Shadow can be called from the clj tool. In the section below will break down both. ## Integration with deps.edn In order to tell Shadow that you want to use a deps.edn you have to add the :deps key to your shadow-cljs.edn. The :deps value is going to Shadow where to look for the theller/shadow-cljs dependency in your deps.edn. If you want to place that in your deps.edn :deps directly then set your shadow-cljs.edn :deps to true Which looks like this: shadow-cljs.edn

{:deps true}

{:deps {theller/shadow-cljs ...}}

shadow-cljs some-shadow-action

{:deps {:aliases [:shadow-cljs]} }

{:aliases {:shadow-cljs {:extra-deps {theller/shadow-cljs ...}} }

{:deps {:aliases [:shadow-cljs]} }

{:aliases {:shadow-cljs {:extra-deps {theller/shadow-cljs ...}
                         :main-opts ["--main" "shadow.cljs.devtools.cli"]}}

clj -M:shadow-cljs pom

clj -M:shadow-cljs pom this won't work so doesn't make for a good example in the last section

otherwise seems accurate

> the command line tool will find theller/shadow-cljs in the deps.edn through the shadow-cljs.edn file.

this isn't entirely accurate. it won't find anything. the clj tool constructs the classpath with shadow-cljs in it, when the process it started it can then be loaded

> clj -M:shadow-cljs pom this won't work so doesn't make for a good example in the last section Oh you right (big surprise 🙂 ) Why does clj -M:shadow-cljs watch app work then? I guess the main function of shadow-cljs.devtools.cli doesn't take the same arguments as the command line then? as shadow-cljs pom would work right?

no, this is not true for all command

as I said yesterday. some commands are provided by the shadow-cljs node script and never execute any java to do that

pom just generates a xml file, it doesn't need java for that

all build related commands require clojure, so they launch java and are available via shadow.cljs.devtools.cli

Thank you! Sorry for not seeing that!