Re: [w3c/webcomponents] Isolate WebComponent JS libraries (#751)

@mmikirtumov I face the exactly same challenge and yes it's micro-frontend approach.
Since those micro SPAs are running in same sandbox the may technically introduce different versions of react, angular or lodash.
I think we have to consider a few things here:

1. Avoid webcomponents include potentially conflicting libraries in dependencies.
 
2. In case you have control over repository and build process I'd suggest leveraging webspaces / monorepo approach where you can get use of peerDependencies and put all actual minimum versions of libraries modules (webcomponents) are compatible with in host package.

3.. It becomes challenging when you have separate builds or compiled webcomponents are served from different location. Then you basically need manually sync your hosting app dependencies with peerDependencies described in webcomponent itself

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/751#issuecomment-435962073