You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for this great invention. It opens up so much possibilities!
For the basic-host-remote example, it looks like I can comment out the whole shared config and I also change to not use bundle-loader or dynamic import, the app button2 still works fine, so what have happen when I did those change? Is this ok thing to do if I don't need omnidirectional host?
The text was updated successfully, but these errors were encountered:
matthewma7
changed the title
What if not use shared in host app
What if not use "shared" in host app
Sep 22, 2020
Sure. So you can choose not to share. But in doing to you'll load multiple copies of the same dependency, a major problem for stuff like react. You only need a import bootstrap if you're sharing something in the entrypoint that's not dynamically imported. If you async imported all the shared modules. Or didn't share, webpack won't have async issues because it's shipping it's own vendors and you're not orchestrating shared code between the apps runtimes. If you added a hook to the remote component. It likely would throw a react error since react needs to be a singleton
Thank you for this great invention. It opens up so much possibilities!
For the basic-host-remote example, it looks like I can comment out the whole shared config and I also change to not use bundle-loader or dynamic import, the
app button2
still works fine, so what have happen when I did those change? Is this ok thing to do if I don't need omnidirectional host?The text was updated successfully, but these errors were encountered: