This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-18
Channels
- # announcements (6)
- # aws (1)
- # babashka (47)
- # beginners (50)
- # calva (65)
- # cider (4)
- # clj-commons (1)
- # clj-kondo (44)
- # clojure (150)
- # clojure-europe (41)
- # clojure-nl (4)
- # clojure-spec (1)
- # clojure-sweden (4)
- # clojure-uk (6)
- # clojurescript (15)
- # clr (1)
- # conjure (1)
- # core-async (7)
- # cursive (5)
- # datomic (12)
- # events (2)
- # fulcro (17)
- # graphql (12)
- # introduce-yourself (1)
- # jackdaw (5)
- # jobs (2)
- # lsp (52)
- # malli (5)
- # meander (3)
- # minecraft (2)
- # missionary (2)
- # off-topic (10)
- # other-languages (9)
- # reitit (9)
- # remote-jobs (1)
- # ring (8)
- # rum (7)
- # shadow-cljs (9)
- # sql (2)
- # tools-deps (20)
- # xtdb (12)
Something like this:
npx shadow-cljs clj-repl --config-merge '{:jvm-opts ["-Duser.home=blah"]}'
In a shadow-cljs project, when my cljs dependency has npm depencies (macchiato has a :npm key in project.clj and a package.json) how do I get shadow to install those npm modules? Do I have to manually install them in my projects package json?
The project has npm declared in their project.clj file. https://github.com/macchiato-framework/macchiato-core/blob/master/project.clj#L19
in general project.clj
is not part of a distributed package. it is only used to generate pom.xml
which actually drives the maven distribution. so the :npm
key does absolutely nothing since it is not transfered to pom.xml
CLJS packages can include a deps.cljs
file with {:npm-deps {"foo" "1.2.3"}}
which would make shadow-cljs run npm install [email protected]
on compile
if the package does not include that file then shadow-cljs doesn't have any info on missing npm packages and can't install them
@U05224H0W thanks for the info! I ended up just coping the npm deps manually.