fix(native-federation): Fix failing build caused by concurrent access to externals metadata. #1058
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
Aukevanoost
requested changes
Feb 6, 2026
Collaborator
Aukevanoost
left a comment
Aukevanoost
left a comment
There was a problem hiding this comment.
Thanks for this! I have one small feedback point.
| const usedPackageNamesWithTransient = addTransientDeps( | ||
| usedPackageNames, | ||
| workspaceRoot, | ||
| config.name |
Collaborator
There was a problem hiding this comment.
This is unfortunately optional and can be empty, could you make the fallback consistent with the behavior in externals caching?
Author
There was a problem hiding this comment.
That makes absolutely sense. To avoid duplicating the logic, I have moved it to the new config-utils file.
Collaborator
|
Appreciate the fix! One question, one more small request: do you mind also fixing this issue in the v4 version? |
Aukevanoost
approved these changes
Feb 6, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The externals metadata are stored individually for each native federation build to prevent build errors.
Context
When running applications using e.g.
concurrently "ng serve mfe1" "ng serve mfe2" "ng serve mfe3" "ng serve vnf-host"the host and all micro frontends are built and launched in parallel. Hence, externals metadata files are also processed in parallel.Since the applications use the same dependency stack, different processes access the same files, which can result in empty files or exceptions such as
EBUSY: resource busy or locked.To avoid build errors, the externals metadata files should be processed and stored separately for each build.