This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-10
Channels
- # babashka (17)
- # beginners (57)
- # calva (19)
- # cider (1)
- # clj-kondo (21)
- # clojure (36)
- # clojure-austin (15)
- # clojure-australia (1)
- # clojure-china (1)
- # clojure-europe (35)
- # clojure-filipino (1)
- # clojure-hk (1)
- # clojure-indonesia (1)
- # clojure-japan (1)
- # clojure-korea (2)
- # clojure-my (1)
- # clojure-nl (1)
- # clojure-norway (5)
- # clojure-sg (1)
- # clojure-spec (6)
- # clojure-taiwan (1)
- # clojure-uk (3)
- # clojurescript (7)
- # clr (9)
- # community-development (5)
- # cursive (14)
- # datalevin (1)
- # emacs (5)
- # events (5)
- # exercism (2)
- # figwheel-main (2)
- # fulcro (6)
- # funcool (3)
- # introduce-yourself (2)
- # joyride (7)
- # leiningen (4)
- # london-clojurians (9)
- # malli (3)
- # membrane (1)
- # missionary (54)
- # music (1)
- # nbb (2)
- # pathom (5)
- # pedestal (55)
- # rdf (13)
- # re-frame (10)
- # reitit (3)
- # shadow-cljs (17)
- # vim (58)
- # web-security (12)
Hi all, the latest release of shadow-cljs seems trigger some issue in our code base. We have a test target that is an npm-module
with compiler options :compiler-options {:external-config {:guardrails {}} :closure-defines {goog.DEBUG true}}}
. We use the target to run jest
tests. Starting the latest release of shadow-cljs, when we run jest we get this error:
● Test suite failed to run
Unable to resolve spec: :expound.spec/specs
at Object.cljs$spec$alpha$the_spec [as the_spec] (test-out/cljs/spec/alpha.cljs:121:18)
at Function.cljs.spec.alpha.spec_impl [as cljs$core$IFn$_invoke$arity$5] (test-out/cljs/spec/alpha.cljs:518:28)
at Function.cljs.spec.alpha.spec_impl [as cljs$core$IFn$_invoke$arity$4] (test-out/cljs/spec/alpha.cljs:513:28)
at Object.<anonymous> (test-out/expound/alpha.cljc:119:1)
at Object.<anonymous> (test-out/com.fulcrologic.guardrails.core.js:10:1)
I noticed that there were changes in the last shadow-cljs release to the npm-module
target, but I have no idea if this is a regression or us doing something wrong, and I'm not sure where to start looking... Any hints on getting to the bottom of this maybe?hmm but :target :npm-module
was entirely broken for release builds for the last few versions?
note that I also did a closure-compiler version bump in that release. in case you have pinned older version
weird that my test didn't catch this. was a pretty big issue what should have affected everything. guess I need to widen my test coverage 😉