Zack Jackson

Also module-federation/typescript now on npm and GitHub

Promise new promise would be a better syntax, the Square braces way of trying to eval things is probably flat in the webpack runtime or module tree, that can lead...

Dm me on twitter, let's do a zoom call. It's possible to use webpacks own script loader to manage actually loading the file. Doing it manually in the promise is...

But it waiting for the promise to resolve. That's kinda how dependency management is supposed to work, app can't start till it's got the tree it needs. But this depends...

I've got a consulting firm so we also do provide staff augmentation if you need longer tee assistance

I'd say importing it below the async boundary is probably the best way to go. Alternatively you can try using dependOn which is relatively new

We had a discussion about this at webpack. About auto installing an async boundary. It's a lot more complicated than it looks unfortunately. However declaring it as async might improve...

Yeah Webpack cannot create a factory for unknown modules. When you use a partial import - webpack crawls the directory and bundles all possible modules. So the graph still has...

If init sharing isn't defined you either don't have federation plugin enabled or are not sharing any modules so the runtime requirement isn't added to webpack since there's nothing for...

So while i cannot support partial remote import paths, i do think you can create a proxy trap to a fake module (maybe) and possibly catch the requested remote, then...