You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to NX 19.8.0, or any other version with updated module federation, builds of all federated remotes with dash in its name started to fail.
Seems like the library property is being ignored. And changing the name property is not possible without renaming the whole project, which is not feasible in our case.
Expected Behavior
Build of federated remotes would pass the same way as before the upgrade.
> nx run acme-remote:build:production
[ Module Federation Manifest Plugin ]: Manifest will use absolute path resolution via its host at runtime, reason: publicPath='auto'
NX [ Module Federation Manifest Plugin ]: no files found for remoteEntry chunk
Pass --verbose to see the stacktrace.
Package Manager Version
No response
Operating System
macOS
Linux
Windows
Other (Please specify)
Additional Information
No response
The text was updated successfully, but these errors were encountered:
belaczek
changed the title
Webpack Module Federation: Remote build fails when dashes are in remote module name
Webpack Module Federation: Remote build fails with dashes in remote module name
Sep 22, 2024
Current Behavior
After upgrading to NX 19.8.0, or any other version with updated module federation, builds of all federated remotes with dash in its name started to fail.
Example federation config:
Seems like the
library
property is being ignored. And changing the name property is not possible without renaming the whole project, which is not feasible in our case.Expected Behavior
Build of federated remotes would pass the same way as before the upgrade.
GitHub Repo
https://github.com/belaczek/nx-federation-repro
Steps to Reproduce
pnpm install
pnpm nx build acme-remote
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: