Luca Trazzi
@lucatrazzi.bsky.social
If you had a monorepo, with a host and couple of remotes, and you would still like to still use lazy imports (to have typesafety from typescript "paths"), what would be your approach to deploy for X environments? Would you build for each environment? What if I want to hotfix a single remote?
November 26, 2024 at 8:46 PM
If you had a monorepo, with a host and couple of remotes, and you would still like to still use lazy imports (to have typesafety from typescript "paths"), what would be your approach to deploy for X environments? Would you build for each environment? What if I want to hotfix a single remote?
Was using github.com/module-feder...
Was not aware of official examples of the vite module federation plugin, great!
Is "dynamic" the correct approach to use for configuring remotes?
Just wanted to replace "localhost:port" with. "realendpoint:port" for each environment with same pkg.
Was not aware of official examples of the vite module federation plugin, great!
Is "dynamic" the correct approach to use for configuring remotes?
Just wanted to replace "localhost:port" with. "realendpoint:port" for each environment with same pkg.
GitHub - module-federation/module-federation-examples: Implementation examples of module federation , by the creators of module federation
Implementation examples of module federation , by the creators of module federation - module-federation/module-federation-examples
github.com
November 26, 2024 at 4:11 PM
Was using github.com/module-feder...
Was not aware of official examples of the vite module federation plugin, great!
Is "dynamic" the correct approach to use for configuring remotes?
Just wanted to replace "localhost:port" with. "realendpoint:port" for each environment with same pkg.
Was not aware of official examples of the vite module federation plugin, great!
Is "dynamic" the correct approach to use for configuring remotes?
Just wanted to replace "localhost:port" with. "realendpoint:port" for each environment with same pkg.