I'm trying to use antizer library in clojurescript (https://priornix.github.io/antizer ) . When I run my build, I get The required namespace "cljsjs.antd" is not available, it was required by "brickmarket/ui.cljs". My deps.edn includes

cljsjs/antd               {:mvn/version "3.12.0-0"}
           antizer                   {:mvn/version "0.3.1"}

i always get this message in chrome console shadow-cljs: reloading code but no :after-load hooks are configured!

although I have put :devtools {:before-load cljs.dev/stop :after-load cljs.dev/start} in my :builds profile

I'm seeing intermittent issues when building a release, where it will fail with the error:

IllegalStateException: could not find where to put constant for module goog.labs.useragent.engine.js
        shadow.build.closure.ReplaceCLJSConstants.process (ReplaceCLJSConstants.java:60)
        ...

it seems to have started occurring in a commit where I split some code out into its own file, with no other changes 😕

@mel.collins that is odd? do you have :depends-on configured correctly?

we're just using a single module at the moment, so we don't have any :depends-on configured

> I split some code out into its own file

what does that mean then?

just an extra ns?

yeah, I had an oversized myapp.views.main, and split out a bunch of the views into their own namespace

that is odd. what is your build config then?

IllegalStateException: could not find where to put constant for module this should only happen when :modules are setup incorrectly. can't explain how it would happen otherwise.

do you have the correct closure-compiler version? yes if using shadow-cljs.end, maybe not if using deps/lein

hmm, if I remove the .shadow-cljs cache dir the build works once, but then fails on subsequent attempts

we're not using deps or lein at this point

that is even weirder. do you do any kind of macro trickery?

(side-effecting macros)

:modules {:main {:entries [myapp.core]}}

I don't think there's any macro trickery

not that we've written anyway. I'm not sure about deps, but the deps didn't change when it started to break

so when it starts breaking

hmm I have no idea how it would even be confused about goog.labs.useragent.engine.js

there are no CLJS constants in that file

so the only time I ever saw this error was with badly defined :modules.

you are using :target :browser I assume?

it doesn't make sense that is only work once as the input to the compiler will be identical to the first one when caching is used

This is :target :npm-module and :runtime :browser

ah!

oh. I guess I need to filter :modules. it is not allowed for :npm-module builds

just use :entries.

:build {:stuff {:target :npm-module :entries [myapp.core]}}

oh interesting, I did not realise

:npm-module desugars to a pretty complex :modules configuration

you just basically added one module it didn't expect so it falls over

hah, well it took its time falling over, since the config has been like that for months! Something about a camel's back 😄

yeah still no idea why it would compile once at all

Yeah, that's fixed that IllegalStateException, thanks.

but we've another branch with the same happening for goog.dom.dom.js, even after with the :entries fix

that branch switched to using deps.edn though, which you mentioned something about?

it is unlikely that this is related to bad dependencies

just make sure to remove :modules from all :npm-module builds

I'll validate and ensure that in the future

yeah, I just checked out a commit prior to the deps.edn change, and it's still complaining about goog.dom.dom.js. But this is after :modules has been removed!

same error?

the heck? This branch is complaining about goog.labs.useragent.engine.js again. Same IllegalStateException, yeah.

could ^:private be a problem?

This branch. are you sure this branch has the updated build config? if you have a server instance running it may still be using an older version too?

no

yeah, I rebased on the updated config, and triple-checked that it was the right shadow-cljs.edn. No server instance running either.

huh, the first time I build I get IllegalStateException: could not find where to put constant for module goog.dom.dom.js, but subsequent times I get the same error but for goog.labs.useragent.engine.js again.

I'm not sure what is happening. I've never seen that error in :npm-module builds before.

if you can please send me the contents of the .shadow-cljs/builds/<your-build>/release directory. its all the cache files and generated JS. maybe I can find something?

and the full build config? maybe there is some other option messing with things

I'm still investigating right now, but I'll zip and send you some stuff after lunch if I don't find anything

make sure you are on the correct directory on the correct machine. wouldn't be the first time that someone was debugging something locally but actually executing something via an ssh connection on a totally different machine 😉

hah yeah, that's always a good one. Sadly not the case in this instance!

okay, so this was unexpected. It seems the mere presence of an :options keyword in any view function is the trigger, even if the function isn't used.

example?

I can use :options in re-frame subs or cljss/defstyles wihtout issue

the keyword is unlikely to be the issue

or rather it is more likely that its the issue WHEN it is used or how

not the keyword itself

lol, now that I've said that I can't get it to break again

cljss does some fairly bad macro stuff. so maybe thats it

right now

(defn secondary-config-mappings
  []
  {:options nil})

defn secondary-config-mappings
  []
  {:optionss nil})

hmm I have an idea

hmm no. not really

huh. If I put (def blah :options) in another file, the error doesn't trigger

but if it's in the same file as the above defn, the error still triggers

@thheller do you still want a copy of the failing build files?

apparently it's not just keywords, but any variable called options triggers it too 😕

on second thought, that might be also related to keywords, since the only occurrences in this code was from deconstructing maps

yeah, a basic function with an options argument didn't trigger the error

@mel.collins yeah the files would help. I cannot reproduce this in any way. build config would also help just in case there is something misconfigured

Does shadow not detect changes to macros for live-reload / compile purposes? Or do we have something configured incorrectly? Just saw a case where we made a change to a macro, saved, nothing kicked off by shadow, changed a line outside of macro and saved, and it behaved normally.

it should support live-reload for macros yes

Hmmm okay. That at least gives us the “Okay something is wrong there” flag. haha. Thanks

totally possible that its not entirely accurate since macros are a bit tricky

Right… I need to read about them a bit more to understand, I think.

Would it change anything that it’s a macro from a library? a Spec macro in this case.

And we only changed how we called it, not the macro itself, I was mistaken before

What is the recommended strategy for developing locally on both client (browser) and server code with shadow? Does it make sense to have two completely separate clj projects? Should I spin up my server project's REPL, start the system, etc....and then configure my client project's :proxy-url to point at the local server? Or maybe it's more appropriate to configure the client's :http-handler to reference the server's main handler fn? This would suggest that the client/server projects are one monolith, or that the client project depends on the server project somehow. Just trying to get a feel for what others have been doing...

@cjsauer I just put all the code in one repo and have multiple builds. easiest to share code that way

@thheller @wilkerlucio thank you, I think I've got it working now :thumbsup: