-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(module-federation): collect secondary entry points from exports #…
…26878 (#27999) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> Some packages that use `exports` in the package.json may point to a directory such as `esm/<entrypoint>`. They would still be imported such as `mypackage/secondary-point`. This needs to be shared still for Module Federation. However, our current logic for finding secondary entry points for packages looks at the sub dirs of the package and tries to match it with the exports fiels. Therefore if `mypackage/secondary-point` was set up such that ``` "./secondary-point": { default: "esm/secondary-point/index.mjs" } ``` then it would never be found correctly, causing share problems. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> exports of secondary entrypoints should be shared correctly ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #26878
- Loading branch information
Showing
2 changed files
with
256 additions
and
1 deletion.
There are no files selected for viewing
This file contains 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
This file contains 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