lein: yes. react-helmet: no

but it's also a react lib/component

lein + :npm-deps you mean yes to ?

Yes, I'm :npm-deps with lein

In my case it's react-currency-masked-input lib/component I'm importing through npm-deps

Ok.

A small difference is that I'm importing it with [react-currency-masked-input :as CurrencyInput]

the component inside react-currency-masked-input is exported as default

In that stackoverflow I noticed they used aget to get the “default”. The correct way to access fields via string is goog.object/get. However, I don’t think that breaks on any cljs versions that I’ve seen (could be wrong).

You also may not be literally doing the same thing as in the example from SO

Yeah, that is my feeling. What caught my attention is that my problem also only occurs with optimizations=advanced

Yeah, that does make it odd

I wonder if it is something to do how the :npm-deps are being processed here

That is a fairly young feature of cljs. I haven’t seen this sort of error before, but haven’t made extensive use of :npm-deps

I was just trying to see if I could see anything that may cause this

are you using a new cljs version as well?

[org.clojure/clojure "1.9.0-beta3"]
                 [org.clojure/clojurescript "1.9.946"]
                 [org.clojure/core.async "0.3.443"]
[reagent "0.7.0"]
                 [re-frame "0.10.1"]

ok

I haven’t been able to find anything still on it. Did you get more of a stacktrace to follow than just: “Uncaught TypeError: Cannot call a class as a function” There is a chance that may shed some light

Not really. Don't know of any knob that I can turn to make it spill a stacktrace or something else

If it happens with a cljs repl connected, you may be able to print *e and see something. However, I’m not sure