This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-08
Channels
- # adventofcode (60)
- # announcements (3)
- # babashka (31)
- # beginners (5)
- # boot (1)
- # calva (13)
- # cider (9)
- # clj-kondo (1)
- # clojure (135)
- # clojure-italy (18)
- # clojure-nl (18)
- # clojure-spec (21)
- # clojure-uk (11)
- # clojuredesign-podcast (1)
- # clojurescript (47)
- # core-async (14)
- # emacs (7)
- # euroclojure (4)
- # fulcro (3)
- # graalvm (19)
- # off-topic (22)
- # reagent (29)
- # shadow-cljs (25)
- # vim (3)
Which of these references to shadow do I really need ? And what about the versions, should they always be the same and how to keep track? project.clj
:dependencies
[[thheller/shadow-cljs "2.8.59"]]
..ideally they should be in sync. if you don't actually use the shadow-cljs
command line then just project.clj
is fine.
then its best to keep them in sync just in case something from the command line changes
I am using project.clj because of Cursive, i 've understood it's needed for dependencies
use shadow-cljs pom
and import the generated pom.xml
in Cursive to create the project
run shadow-cljs pom
again to update later, Cursive will pick up the changes automatically
alright, thank you. I also noticed that shadow version has somehow changed to node: v13.2.0
My project is at node 10.x , it won't clash, will it?
on another topic: can I safely manualy delete the target, node_modules
folders ? I keep carrying some old libraries I am not using anymore..
target
yes, if you have a package-lock.json
or yarn.lock
(if you use yarn
) then you can delete node_modules
"safely"
yes, but without a yarn.lock
file the result of rebuilding them can be quite different
Isn't yarn is taking all the relevant dependencies form package.json and installs them anew?
read up on non-determinism regarding npm/yarn. eg. https://yarnpkg.com/blog/2017/05/31/determinism/
all of npm uses version ranges. so you might have had version 1.5
or something and get 1.8
after a new install