Tom Sherman

@dsherret Maybe it could be possible to leverage https://github.com/swc-project/swc/tree/main/crates/swc_bundler for figuring out the dependency graph and performing the tree shaking

For now I'm doing two builds: one for testing purposes that includes all the relevant shims in dev and non-dev code, and another that includes no shims intended for publishing...

Are we able to merge this once the conflict has been resolved?

I've done some experimenting on my own minifier-in-a-browser (https://github.com/tom-sherman/yet-another-js-online-minifier) Turns out that only some of the freeze up is caused by the minification, the rest is caused by just pasting...

What have you tried? What hasn't worked? I'd expect `useNavigation().navigate()` to work just fine, or passing props through from the route prop (that includes `navigation`)

I have attempted a few things, setting `eager: true` and also attempting to defer registration of the root component using `registerRunnable` and `runApplication `. Neither seem to work.

I'll try and spin up a repro 👍

Actually @zamotany if you're saying this is impossible right now I suppose it's not worth me spinning up a reproduction? Can you explain what makes this not possible? I assume...

@zamotany FYI I spoke to @ScriptedAlchemy about this one and we came to the conclusion that this should be possible. To clarify above, I wasn't referring to federating react or...

Yup sure, I mean being about to do `import something from "federated-module"` where "federated-module" is some federated remote module. Instead of doing `import("federated-module")`