figwheel-main 2020-06-02

didibus10:06:02

[Figwheel] Failed to compile build prod in 0.025 seconds.
[Figwheel:WARNING] Compile Exception: contains? not supported on type: java.lang.Boolean  
[Figwheel:SEVERE] contains? not supported on type: java.lang.Boolean
Execution error (IllegalArgumentException) at cljs.closure/compute-upstream-npm-deps$fn (closure.clj:2440).
contains? not supported on type: java.lang.Boolean

I get this when trying to build with :target :bundle ?

folcon10:06:18

Yes, update clojurescript to 1.10.773 should help =)…

bhauman12:06:12

@U0K064KQV ^

didibus18:06:39

That's the version I am using

didibus18:06:22

Along with fighweel "0.2.7"

didibus19:06:21

Seems to be caused by me having :install-deps true in my config

didibus19:06:49

:clojure.main/message
 "Execution error (IllegalArgumentException) at cljs.closure/compute-upstream-npm-deps$fn (closure.clj:2440).\ncontains? not supported on type: java.lang.Boolean\n",
 :clojure.main/triage
 {:clojure.error/class java.lang.IllegalArgumentException,
  :clojure.error/line 2440,
  :clojure.error/cause
  "contains? not supported on type: java.lang.Boolean",
  :clojure.error/symbol cljs.closure/compute-upstream-npm-deps$fn,
  :clojure.error/source "closure.clj",
  :clojure.error/phase :execution}

folcon19:06:00

Check your deps tree? you might be running a different version than you think you are… (I’ve done this..) With deps.edn it’s clj -Stree and with lein it’s lein deps :tree

didibus19:06:30

Hum, checked -Stree, still shows org.clojure/clojurescript 1.10.773

bhauman20:06:51

@U0K064KQV it really shouldn’t be happening with that version

didibus20:06:11

Hum, something else that happens is that it doesn't se to apply the bundle-cmd after the build

didibus20:06:20

I have to manually run it

ingesol13:06:52

Hm, I’m using 0.2.7 and building with auto-test, seems auto-test is overwriting the regular main.js:

[Figwheel] Successfully compiled build basedev to "resources/public/js/main.out/index.js" in 42.267 seconds.
[Figwheel] Bundling: npx webpack --mode=development resources/public/js/main.out/index.js -o resources/public/js/main.js
[Figwheel] Outputting main file: resources/public/js/main.out/index-auto-testing.js
[Figwheel] Bundling: npx webpack --mode=development resources/public/js/main.out/index-auto-testing.js -o resources/public/js/main.js
[Figwheel] Watching paths: ("src/clojure" "test/clojure") to compile build - basedev

bhauman13:06:26

@ingesol what are your compiler options?

ingesol13:06:35

@bhauman

{:main            my.main
 :output-to       "resources/public/js/main.out/index.js"
 :auto-testing    true
 :output-dir      "resources/public/js/main.out",
 :asset-path      "/js/main.out"
 :closure-defines {"re_frame.trace.trace_enabled_QMARK_" true}
 :preloads        [my.preloads]}

ingesol13:06:07

figwheel-main.edn

{:auto-testing       true
 :watch-dirs         ["src/clojure" "test/clojure"],
 :css-dirs           ["resources/public/css"],
 :open-url           "false"
 :helpful-classpaths false
 :auto-bundle        :webpack
 :final-output-to    "resources/public/js/main.js"}

bhauman13:06:50

well that’s a bug then

ingesol13:06:10

could it be the specification of :final-output-to?

bhauman13:06:33

no it’s a bug I must have introduced recently

bhauman13:06:01

final-output-to is supposed to be munged

ingesol13:06:22

I THINK I tested this with both auto-test and in main somewhere on 0.2.7-SNAPSHOT

bhauman13:06:48

I refactored