-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module Federation emits zero-sized files #20428
Comments
Hi @glebmachine, Thanks for opening this issue. While the Angular CLI allows extending the Webpack configuration by doing so you are venturing on the unsupported path as Angular tooling team doesn't provide support for builds using custom Webpack configurations. I suggest that you file an issue https://github.com/angular-architects/module-federation-plugin and raise an issue with the author of this package. My initial though here are that they need to provide a custom logging function that handles the information provided by Webpack when using Module Federation. |
@alan-agius4 here is a repro without manfred's plugin. Please reopen Related to feature request: #17556 |
I messaged you on Twitter @glebmachine. Perhaps you can open this issue in the CLI repo? I'd like to help you get this going. @BenRacicot |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🐞 Bug report
Command (mark with an
x
)Is this a regression?
It's early version bug
Description
It's report about early support of webpack 5 and module federation.
A clear and concise description of the problem...When internal library added as shared dependency, cli emits zero-sized files
🔬 Minimal Reproduction
Repro:
git clone [email protected]:glebmachine/module-federation-zero-sized-bundle.git
yarn
./node_modules/.bin/ng run shell:serve
Step to
repair build
:projects\shell\webpack.config.js
🔥 Exception or Error
See picture above
🌍 Your Environment
Anything else relevant?
The text was updated successfully, but these errors were encountered: