Replies: 1 comment 4 replies
-
The value is basically passed to node.js I would recommend to create (or generate) a package.json for the dist assets like that: {
"dependencies": {
"@remotes/website2": "http://containers.my.company/website2.tar.gz"
}
} with new ModuleFederationPlugin({
// ...
remotes: {
website2: "@remotes/website2"
}
// ...
}) and run a Note: Alternatively you can use a custom npm registry where you deploy your compiled containers to. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I followed some examples from: https://github.com/module-federation and came across this server.base.js (link to exact exampel) webpack config.
So I wonder if remotePath for the server side can also be a real remote address (eg: remote1: 'http://some.cdn.com/server/remote1/remote-entry.js',) like in the clients config. I tried but can't get it woking. If not what would be the recommended way if website1 and website2 are deployed to different servers/pods?
Cheers, Tim
Beta Was this translation helpful? Give feedback.
All reactions