Module federation should declare the remote entries with its location

Feature request

Let’s start from this example.

The app1 (shell/main/host) depends on app2. This dependency is declared in the webpack.config.js, but the location of app2 is declared in the /public/index.html

What is the expected behavior? I’d like to see them togheter, in the plugin options

    new ModuleFederationPlugin({
      name: "app1",
      library: { type: "var", name: "app1" },
      remotes: {
        app2: {alias: "app2", remoteEntry: "http://localhost:3002/remoteEntry.js"}
      },
      shared: ["react", "react-dom"],
    }),

What is motivation or use case for adding/changing the behavior? Easier to maintain

How should this be implemented in your opinion? It should not change the core behaviour. It’s like a syntax sugar: just copy the remotes.{key}.remoteEntry to the index.html as <script>

Are you willing to work on this yourself? I’d love to. Not sure if I know enough about webpack’s implementation.

[kenkozheng]

I partly agree with u. Declare in the index.html is not a good idea. But if declaring in the config file, the url of app2 will just be static. For example, we want to get the url of app2 from an admin backend.
Actually, I want webpack do the favor for me to finish the last step, not fetching remoteEntry.js by my code.

[whu12yz]

remoteEntry

how? could u please give an example @zhangwilling