This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-01
Channels
- # adventofcode (2)
- # announcements (3)
- # babashka-sci-dev (79)
- # beginners (76)
- # biff (2)
- # calva (32)
- # cider (2)
- # clj-kondo (42)
- # clj-on-windows (17)
- # clojure (28)
- # clojure-belgium (1)
- # clojure-berlin (1)
- # clojure-europe (95)
- # clojure-nl (4)
- # clojure-norway (4)
- # clojure-uk (5)
- # clojurescript (27)
- # conjure (5)
- # cursive (3)
- # data-science (16)
- # datomic (67)
- # graalvm (12)
- # hyperfiddle (36)
- # jobs (3)
- # jobs-discuss (1)
- # kaocha (2)
- # klipse (1)
- # leiningen (28)
- # lsp (16)
- # luminus (3)
- # malli (10)
- # nrepl (3)
- # off-topic (57)
- # other-languages (18)
- # re-frame (4)
- # reitit (8)
- # releases (1)
- # remote-jobs (1)
- # scittle (4)
- # shadow-cljs (7)
- # test-check (1)
- # tools-deps (4)
- # vim (11)
- # xtdb (25)
Can :js-options :resolve
be used only to re-route requires from cljs code or the config will also affect JS require/import
declared in required NPM modules?
My use case is the following: NPM package X
depends on Y
, but I have replaced Y
with a local custom build. This works fine as long as NPM stuff is built by Webpack that also has resolve config. Now that I want to require X
directly in CLJS namespace and let Shadow bundle it, I also want to make sure that given resolve config in shadow-cljs.edn
Shadow will take care of resolving local Y
for NPM package X
.
Oops, should have probably posted this in this thread to start with.
Hmm I'm trying to update noencore, but I can't figure out how.. it doesn't appear to be listed in my package.json or shadow-cljs.edn files