-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
fix(enhanced): Do not inject the federation runtime into build time chunk #3225
Comments
Send a pull request |
6 tasks
lnlfps
added a commit
to lnlfps/mf-core
that referenced
this issue
Nov 15, 2024
ScriptedAlchemy
added a commit
to lnlfps/mf-core
that referenced
this issue
Nov 16, 2024
ScriptedAlchemy
added a commit
to lnlfps/mf-core
that referenced
this issue
Nov 17, 2024
Can you create a test case in enhanced/test/configCases that fails the test so that we can debug your branch against a failing test case |
lnlfps
pushed a commit
to lnlfps/mf-core
that referenced
this issue
Nov 18, 2024
…federation#3225)' of github.com:lnlfps/mf-core into fix/do-not-inject-runtime-into-build-time-chunk(module-federation#3225)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When working with umijs or father, during the compilation of less modules, some 'build time chunks' are generated. These temporary chunks lack chunkGraph information, leading to errors when generating runtime code.
Then The current chunk id is
build time chunk
, the variablethis.compilation.chunkGraph
isundefined
,causing an exception to be thrownSuggestion
If the chunk's id is
build time chunk
, do not inject the federation runtime to this chunk. like this:Reproduction
Used Package Manager
npm
System Info
Validations
The text was updated successfully, but these errors were encountered: