This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-20
Channels
- # aws-lambda (7)
- # beginners (113)
- # boot (17)
- # cider (4)
- # cljs-dev (4)
- # clojure (65)
- # clojure-greece (3)
- # clojure-italy (7)
- # clojure-russia (10)
- # clojure-spec (37)
- # clojure-uk (20)
- # clojurescript (76)
- # community-development (2)
- # cursive (24)
- # data-science (9)
- # datomic (9)
- # emacs (1)
- # fulcro (2)
- # graphql (11)
- # hoplon (13)
- # juxt (15)
- # leiningen (1)
- # off-topic (36)
- # om (1)
- # onyx (59)
- # parinfer (41)
- # pedestal (7)
- # portkey (60)
- # protorepl (4)
- # re-frame (345)
- # reagent (7)
- # ring-swagger (16)
- # shadow-cljs (121)
- # spacemacs (30)
- # sql (6)
- # uncomplicate (2)
- # unrepl (9)
- # vim (13)
- # yada (2)
hmm, cljs :npm-deps installation appears to be removing other, valid deps that are in package.json
and installed into node_modules
.
example w/ fairly minimal template with transitive React :npm-deps --
lein new re-view xyz;
cd xyz;
yarn install;
…node_modules/shadow-cljs and shadow-cljs-jar exist…
lein figwheel;
…node_modules/shadow-cljs is empty and shadow-cljs-jar is removed…*appears to be a bug with NPM 5, https://github.com/npm/npm/issues/17929#issuecomment-319722758
so in NPM 5, running npm install <something> --save
deletes other things in node_modules
, even if they are listed in package.json, if npm install
has not already been run. so anyone running yarn could encounter it. i think running npm install
before any npm install <dep> --save
would prevent this. blah.