I'm trying to make a chrome extension, there is many moving parts, so i output the extension itself to resources/public/js/extension and set the output-dir for the background script in resources/public/js/extension/background. Compilation works, then I add the extension to chrome targeting resources/public/js/extension (where my extension manifest is). The trouble is that now chrome is looking for the modules with /resources/ as root rather than resources/public/js/extension So how can i ask shadowcljs (or maybe the clojurescript compiler?) to root the js lookup in resources/public/js/extension` ?

In other words, right now chrome tries to load but i want it to try loading

ah got it :asset-path "/background"

now for hot code reloading ...shadowcljs is trying to open a websocket at .... which of course doesn't work, how can i tell it to use my already running server at ?

ah for posterity : :devtools-url "" in :devtools key of shadow-cljs.edn

@carkh its not documented well but shadow-cljs can build chrome-extension directly which fixes all those issues https://github.com/thheller/shadow-cljs/issues/279

oh wow, i've been worrying about the module thing, but didn't investigate that yet

nice

didn't have any trouble with switching repls though

looking at the issue, you have browser-action and content-script, is it also possible specify the options-page ?

that's another compilation that might benefit form modules

it probably is yeah

haven't looked at it in a while but I think I covered all possible built targets

very nice, i'll try to switch to this new workflow and maybe tell you how it goes if you'd like that

since its all built on modules you can pretty much build everything

since all that really matters is how the code gets loaded

opts pages looks the same as the other html driven options

so you can probably set :output-type :chrome/page-action for the module

sorry ... this stuff really needs docs

don't be sorry, already awesome that this exists at all

here is one extension that uses this stuff maybe that helps in some way https://github.com/fulcrologic/fulcro-inspect/blob/master/shells/chrome/manifest.edn

https://chrome.google.com/webstore/detail/fulcro-inspect/meeijplnfjcihnhkpanepcaffklobaal

hah i'm using it, and actually am using fulcro for the options page

is using eval from the shadow-cljs repl supported?

i'm seeing:

[0:0]~cljs.user=> (eval '(+ 1 2))
Error: cljs.core/*eval* not bound

is there some other setup i need to do

@nickmbailey afaik there is no eval with clojurescript

self hosted clojurescript probably has it if necessary

i see

@nickmbailey eval in CLJS requires using the self-hosted compiler. shadow-cljs does support building everything you need for that but doesn't run it itself. see https://code.thheller.com/blog/shadow-cljs/2017/10/14/bootstrap-support.html

@thheller so i switched to the :chrome-extension target as we discussed. And I hit the repl switching problem. I have several running javascript instances under the single chrome-extension build, and i can only invoke the repl on a per build basis... any workaround i should be aware of ?

if you are using nrepl not really no

mhh that's a problem, no auto-completion in cider when in the wrong repl ... too bad i like that whole build target thingie =(

thanks anyways !

auto completion should work. I don't think that calls eval?

i don't quite know why but it doesn't ... when in a build's repl that doesn't "link" to the current buffer no auto-complete in cider

probably uses some nrepl magic to get the live state

very much not my expertise =)

that all should work since it shouldn't try to eval

eval is the only issue since with multiple runtimes it is not clear how to do that consistently

but I know nothing about cider so can't help much

no big deal i'll go back to the old way which was working fine, in the meantime i got better organisation out of this escapade

too bad i'll be losing the modularisation, maybe just use the chrome-extension target for release

is there a way to dynamically define vars in clojurescript?

i'm using intern in a macro in clojure but thats not available in clojurescript

(was previously playing with eval, hence the earlier question)

dynamically as in a macro yes, at runtime no

well it should be fine to happen at compile time but eval wasn't working so i switched to intern which lets it happen at runtime

so i guess i can switch to self hosted clojurescript

and eval

what are you trying to do exactly?

typically you should just have the macro emit (def ...) forms

the super dynamic clojure style Var creation via actual Var calls will not work even in self-hosted CLJS since there are no vars at runtime

i'm making a macro that makes builder fns for plumatic/schema map keys so:

(crazy-macro foo {:a Int})

foo-a

(crazy-macro bar (merge foo {:b Int}))

in regular clojure just eval'ing the form works, or using intern to inject the vars at runtime also works

why does it create vars?

well they are builder functions

it creates vars via defn

what does that mean? 🙂

builder functions sound like OOP mess to me?

heh i don't disagree with that

its a bit of a crazy idea

if you can stomach adding several megabytes of JS to your build I guess self-host is something you can try

but otherwise I would probably look for better solutions

yeah i'll probably abandon this for clojurescript for now heh

it seems like when shadow-cljs is compiling a .cljc file and it runs into a reader conditional it picks the ":clj" option

if you are loading the ns as a macro yes

hmm why is that?

hmm? its the same as anywhere else?

macros in CLJS are written in Clojure

right, i'm trying to make the macro do nothing in clojurescript

any particular reason you are writing that in a .cljc file?

.cljc is kinda mind bending when it comes to macros and stuff so I would recommend avoiding it as much as possible

you can't use reader conditionals to decide what code a macro should emit

hmm well i'm trying to use reader conditionals around the defmacro call completely

#?(:cljs (defmacro...) :clj (defmacro...)

yeah thats not gonna work 🙂

heh

that would be for self-hosted macros

ok but i should be fine if i just split into clj and cljs files?

the trick commonly used in macros that should emit different code for CLJ or CLJS is checking the &env

ah

#?(:clj (defmacro foo [& args] (if (:ns &env) :cljs :clj)))

so (foo 123) used in CLJS will end up just returning :cljs

and :clj if called in CLJ

you need (ns the.ns #?(:cljs (:require-macros [the.ns]))) self-require for macros

hmm i'm using :refer-macros

is that the same?

no

well yes ... but don't do that. this way is much simpler.

lets others using the.ns completely skip worrying about macros and just use them as you would in CLJ

ah i put that in the file where the macro is defined

got it

so (ns (:require [the.ns :as x])) (x/foo) works

@thheller that got me up and running, thanks for the help!

and more generally thanks for shadow-cljs heh