Fork me on GitHub
#shadow-cljs
<
2022-09-01
>
Roman Liutikov11:09:07

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.

thheller17:09:51

yes, it applies everywhere not just cljs

James Pratt11:09:15

Oops, should have probably posted this in this thread to start with.

Ryan19:09:34

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

Ryan19:09:53

I added [noencore/noencore "0.3.7"] to shadow-cljs.edn and it updated.. not sure what caused it to be required in first place tho

thheller19:09:23

one of your other dependencies probably. shadow-cljs does not require it

🙏 1