Great, will let you know if I find anything

any idea how one can resolve an issue like this:

[:browser] Build failure:
symbol module$node_modules$object_assign$index already provided by [:shadow.build.npm/resource "node_modules/object-assign/index.js"], conflict with [:shadow.build.npm/resource "node_modules/object.assign/index.js"]
{:provide module$node_modules$object_assign$index, :conflict [:shadow.build.npm/resource "node_modules/object-assign/index.js"], :resource-id [:shadow.build.npm/resource "node_modules/object.assign/index.js"]}
ExceptionInfo: symbol module$node_modules$object_assign$index already provided by [:shadow.build.npm/resource "node_modules/object-assign/index.js"], conflict with [:shadow.build.npm/resource "node_modules/object.assign/index.js"]
	clojure.core/ex-info (core.clj:4739)
	clojure.core/ex-info (core.clj:4739)
	shadow.build.data/add-provide (data.clj:74)
	shadow.build.data/add-provide (data.clj:69)
	shadow.build.data/add-provides/fn--19031 (data.clj:87)

the module auth0 depends on object.assign (and I use that in my web build), while postcss-loader uses object-assign (not used in web build)

hehe nice

I can probably change the alias generator to account for that, guess google didn’t anticipate something like this

will take a look later

but if the postcss-loader isn’t used in the build why does it get resolved?

seems like it is used somehow?

it’s in package.json as it is used for a build script,

but it shouldn’t have anything to do with the shadow build

doesn’t matter if its in package.json

it only matters if the dependency gets added to the build via some :require

ok. i removed postcss entirely, lets see..

super weird that there are actually object-assign and object.assign packages

maybe i am just not using auth0 properly

yeah i am using the node version

so it is requiring unfriendly things

if the things are compatible

you can just :resolve {"object.assign" {:target :npm :require "object-assign"}} or the other way

I’ll be back later …

using auth0-js instead of auth0 package solved this thing in particular. but this clash could be a more general thing. I think the resolve option as you specify there might be ‘enough’. at some point down the chain, the dev has to manually resolve conflicts.

good to know. dunno how common this issue might be. the potential for conflict exists and should probably be fixed nonetheless.