Yeah nx doesn't have a wrapper for it yet

I just like the import from style for MFE and many others did too. But that my personal preference others followed. Federation works with many other patterns. LOSA is what single spa uses. That works too.

But byte had unified infra. So, the infra team controls most aspects like this in our meta frameworks. These problems are primarily experienced by outside users, hence the bridge layer.
Alternatively, you can do older school LOSA architecture, which is immune to this particular issue.

We also control all package versions via a server since federation is bound to vmok in house. So we just change a drop down selection to adjust supply chain. If there's a incompatibility then either we pin those to versions that work or enable the bridge till end user updates on their own time.

Internally we bake the framework bridges into a runtime plugin. So the system automatically detects incompatible majors and will wrap the imported module in an adapter on the way to the consumer. So consumer wouldn't even know. Externally we just expose the bridge system so less witchcraft

Yeah. So this is a problem of my own making with the import from polylith style.
1. we have share scope, allowing multiple singletons
2. we provide adapter and framework bridges allowing you to mount other apps or majors

Please go fix react 😅

Lil bro > Dax

Whats your raw rolldown speed expected if js wasn't bottlenecking it? Pretty good speedup for drop-in. Rspack does about 3x when babel loaders are used heavily.

You beat me to it

Federation examples repo/runtime-plugins/remote-router or one of the other ones.
Also Federation already supports remote types, as does using it at runtime with loadRemote instead of import.

But federation would see the key in its cache and just use the first one it found. Meanwhile I need to load it again and change it's source. So the key can't just be what the request is. Since "react" is technically two different modules now.

The problem with module sharing is it does not carry layer info. So if the import is "react" the resolver cache thinks it's already fulfilled, returning the first react variant that matches. But layers means you can import react again and it resolve to something else.

Yeah. Basically any time you could not statically know what it is you want. Like you can do dynamic remotes with runtime plugin if all you want to do is swap out the urls etc. But if you needed to import(unknown/unknown) and there's nothing you know to configure at compule time then dynamic is 👌

Call me crazy. But we should buy it 😆

Hey, just in case you didn't see. There's some ssl/tls upgrades coming

Watch them just fork chromium and ship another one within weeks.

Bundlers should be language agnostic from the get go.