-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Open
Description
This time it's @sokra who told me this is probably the place to open an issue.
- Operating System: Windows 10
- Node Version: 12.16.2
- NPM Version: 6.14.4
- webpack Version: 5.0.0-beta.22
- webpack-dev-server Version: 3.11.0
- Browser: Chrome 84.0.4147.105, Firefox 79.0, Edge 84.0.522.48
- This is a bug
Code
https://github.com/codepunkt/module-federation-examples/tree/dynamic-host-remote
Expected Behavior
Using webpack-dev-server instead of webpack should still support module federation with additional content tacked onto the remoteEntry by defining it as an additional entry.
Actual Behavior
Running "yarn start" to start webpack-dev-server breaks module federation and thus breaks the app in development mode.
For Bugs; How can we reproduce the behavior?
- clone repository
- ensure you're on branch "dynamic-host-remote"
- run
yarnon repo root - go into "dynamic-host-remote" directory
- run
yarn startin "dynamic-host-remote" directory - open
localhost:3001in the browser - encounter an error in the browser console that happens when executing app2/remoteEntry.js with the additional contents that were added to this entrypoint by
webpack-dev-server - OPTIONAL: run
yarn build && yarn serveand revisitlocalhost:3001to see production build working just fine.
robinbullock, raphaelsantos-hotmart, codetker, csvan, menosprezzi and 7 moremenosprezzi, ryan-olejnik and IgorStetsiukcodetker, csvan, estevaolucas, ryan-olejnik and ssuvorov