Skip to content

Failing build caused by concurrent access to externals metadata on Windows. #1059

@fzankl

Description

@fzankl

With what library do you have an issue?

native-federation

Reproduction of the bug/regression with instructions

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.

In the following extract of the build output the build fails due to the peer dependency zrender of Apache echarts. However, it could also be any other dependency, as this is completely random.

Image

Expected behavior

Build should succeed without exception

Versions of Native/Module Federation, Angular, Node, Browser, and operating system

@angular-architects/native-federation: 21.1.0
Angular: 21.1.2
Node: v24.13.0
OS: Windows 11

Other information

Link to PR resolving the issue #1058

I would be willing to submit a PR to fix this issue

  • Yes
  • No

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions