Try to compile into es6 by setting the argument in your shadow-CLJS.edn file

(Maybe update to 2.83?)

@jmckitrick that is caused by you using project.clj or deps.edn and not having the correct closure-compiler version (ie. dependency conflict). you need to resolve this, you should have

[com.google.javascript/closure-compiler-unshaded "v20191027"]

   [org.clojure/google-closure-library "0.0-20191016-6ae1f72f"]
   [org.clojure/google-closure-library-third-party "0.0-20191016-6ae1f72f"]

I think its time I write this down somewhere ... getting tired of repeating it ... why does everyone insist on using lein/deps.edn?

(note that the version changes between shadow-cljs versions, so if you have one pinned you must make sure it matches) ... or just use shadow-cljs.edn ....

deps.edn allows local libraries or git libraries

yeah I know

Hi! In JS I can do const logo = require('../../media/logo.svg'); and then use logo as html (e.g. in React's dangerouslySetInnerHTML={{ __html: logo }). What to people do in Cljs / shadow? I guess it is not supported to require a non-cljs resource. Thank you!

I’m perfectly happy using a better method, as long as I can build an uberjar with the result. Is there a better way?

I had removed the shadow code from the project.clj, but put it back for building the uberjar.

@jmckitrick shadow-cljs release app && lein uberjar would be my recommendation. I really don't see the point lein doing everything but some people prefer that.

Hmm, that’s what I was doing.

Let me try again, and post the results here.

~/d/b/bank1 ❯❯❯ shadow-cljs release app                                                                                                                                ⏎ master ✱
shadow-cljs - config: /Users/jmckitrick/devel/bank/bank1/shadow-cljs.edn  cli version: 2.8.69  node: v13.7.0
shadow-cljs - running: lein run -m shadow.cljs.devtools.cli --npm release app
NPM version conflict for "react" in deps.cljs (will use A)
A: "16.8.6" from jar:file:/Users/jmckitrick/.m2/repository/re-frame/re-frame/0.10.9/re-frame-0.10.9.jar!/deps.cljs
B: "16.9.0" from jar:file:/Users/jmckitrick/.m2/repository/reagent/reagent/0.9.0-rc3/reagent-0.9.0-rc3.jar!/deps.cljs
NPM version conflict for "react-dom" in deps.cljs (will use A)
A: "16.8.6" from jar:file:/Users/jmckitrick/.m2/repository/re-frame/re-frame/0.10.9/re-frame-0.10.9.jar!/deps.cljs
B: "16.9.0" from jar:file:/Users/jmckitrick/.m2/repository/reagent/reagent/0.9.0-rc3/reagent-0.9.0-rc3.jar!/deps.cljs
[:app] Compiling ...
IllegalArgumentException: No matching field found: getSourceName for class com.google.javascript.jscomp.JSError

as I said before. you are running through lein. so YOU must ensure that the shadow-cljs version in project.clj gets the matching closure-compiler version it expects

from the looks of it you actually have a newer version of shadow-cljs in project.clj, not .69.

Ok, let me fix that.

But I wasn’t using lein there…

I used it for setup

> shadow-cljs - running: lein run -m shadow.cljs.devtools.cli --npm release app

if :lein is configured in shadow-cljs.edn it will use lein to run things

I see… lein true

if you remove that it will run shadow-cljs directly without lein

BUT then you must move your dependencies and source-paths into shadow-cljs.edn as well

Ok, I think that’s the next step. I thought it was solved when I just deleted the shadow keys from project.clj

I will come back to this. As long as I know I can get an uberjar for prod deployment, I can revisit the topic later.

Thanks for you help, meanwhile!

uberjar will just copy all the files in the paths you have configured

The build did get farther, but broke looking for the correct namespace. I assume that’s what you were referring to, with setting up shadow-cljs.edn correctly with dependencies and paths.

so if you have shadow-cljs output the files into a dir you want packaged

then it'll just work

yes, source-paths

I think I’ll start over, and begin with reading the manually entirely 😉

Are there any examples or articles on building :chrome-extension with shadow-cljs? I couldn't find any so far. Thanks!

@rberger this is all that exists in terms of docs https://github.com/thheller/shadow-cljs/issues/279

the fulcro-inspect extension uses it

Thanks, saw the issues but will check out the fulcro-inspect, that should help... Also want to thank you so much for shadow-cljs. It really makes Clojurescript work wonderfully! Really helped in allowing us to take advantage of things like AWS Amplify: https://dev.to/rberger/aws-amplify-and-clojurescript-re-frame-part-1-3d3f

Couldn't have made that work without shadow-cljs