This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-11
Channels
- # architecture (3)
- # beginners (41)
- # boot (7)
- # cider (16)
- # cljs-dev (8)
- # cljsrn (2)
- # clojure (214)
- # clojure-austin (4)
- # clojure-russia (52)
- # clojure-spec (8)
- # clojure-taiwan (1)
- # clojure-uk (10)
- # clojurescript (87)
- # cursive (14)
- # datascript (34)
- # datomic (11)
- # dirac (55)
- # emacs (12)
- # hoplon (44)
- # luminus (6)
- # lumo (24)
- # off-topic (1)
- # om (8)
- # onyx (7)
- # overtone (2)
- # pedestal (1)
- # protorepl (4)
- # re-frame (7)
- # reagent (1)
- # ring (4)
- # rum (2)
- # slack-help (1)
- # spacemacs (2)
- # specter (32)
- # unrepl (131)
- # untangled (14)
- # yada (3)
Just created and attached a patch to http://dev.clojure.org/jira/browse/CLJS-1973
this is the 2nd part of the solution outlined in this design doc: https://github.com/clojure/clojurescript/wiki/Enhanced-Node.js-Modules-Support
It makes is possible to specify :npm-deps
in deps.cljs
files too, and includes basic conflict handling too
/cc @juhoteperi this might be interesting for you to try out
Hmmh, this still calls npm?
yeah, it calls NPM
just like specifying :npm-deps
in the compiler options will also shell out to NPM to install the modules
@anmonteiro: I'm not sure if I totally understand the ramifications of all of this in relation to current tooling. Would this be the prereq for something like cljsjs with node, where there would be additional work required as new libraries are set up or brought in? Or does it lead more towards consumers of an npm library being able to treat npm just like clojars (assuming the tooling is in place)? Either way, awesome and exciting work!