This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-19
Channels
- # announcements (1)
- # architecture (8)
- # babashka (8)
- # beginners (68)
- # biff (1)
- # calva (2)
- # clj-kondo (13)
- # cljs-dev (2)
- # clojure (71)
- # clojure-art (26)
- # clojure-europe (14)
- # clojure-nl (10)
- # clojure-uk (4)
- # clojurescript (96)
- # community-development (6)
- # conjure (1)
- # datalog (2)
- # emacs (6)
- # fulcro (20)
- # hugsql (7)
- # lsp (6)
- # nextjournal (13)
- # off-topic (7)
- # portal (1)
- # reagent (3)
- # reveal (8)
- # sci (50)
- # shadow-cljs (8)
- # spacemacs (2)
- # tools-deps (9)
- # xtdb (6)
I'm having a problem with a compile using the wrong version of a dependency (using the project’s version project/node_modules
instead of the local module's project/module/node_modules
). Is there a way to enable verbose logging to get more details on the situation?
I've tried to isolate the issue by constructing a simple version of the problem but I wasn't able to reproduce it. It's probably an edge case or something specific to my setup.
if its a browser build you get generate a build report. that lists everything that was used and why https://shadow-cljs.github.io/docs/UsersGuide.html#build-report
I was able to resolve my issue by using clojure -M:shadow-cljs compile ...
rather than npx shadow-cljs compile ...
I know a bit more now: this seems to have been caused by an old version of shadow-cljs being specified in deps.edn
. A newer version was used in package.json
but it seems shadow-cljs will prefer using the clojure-cli one?