shadow-cljs watch a node library often tells me this: [:d3-cljs] Build failure: The required namespace "shadow.umd-helper" is not available. But it is working well, just do not know what this means.

odd

indeed. I can reproduce. looking into it.

@cmal fixed in [email protected].

:thumbsup:

@cmal saw your fork. you can now use [email protected] and specify :devtools {:use-document-host false} which changes the default behaviour and then uses the :host specified in :http {:host ...} which defaults to "localhost" instead of js/document.location.hostname

any reason we use manifest.json rather than *.edn?

way back when I introduced the feature I was using a ruby script for deployment. it was easier to use .json files, thats pretty much the reason. never changed it since.

I had an issue the other day with two npm dependencies clashing. Specifically object-assign and object.assign. How are these npm dep names munged?

ah hehe you are not the first to run into that one

munging is done by (ModuleNames/fileToModuleName js-name)

which is a utility function from the Closure Compiler

which we kinda have to use unfortunately

you can use :resolve {"object-assign" {:target :npm :require "object.assign"}}

so only one is included, assuming that they both do the same thing

https://code.thheller.com/blog/shadow-cljs/2017/11/10/js-dependencies-in-practice.html#redirecting-require

Ah, okay

I assume they’re both polyfills, but I’d have to check

Thanks!

looks like they are doing the same thing yes.

the amount of polyfills npm packages depend on is scary.