nx
nx copied to clipboard
fix(angular): add check before attempting to collect secondary entrypoints #11437
Current Behavior
A lib that has the same starting name as another library forces an infinite loop when checking for secondary entry points
Expected Behavior
We're checking all libraries for secondary entry points, when we should only check those that might contain it.
This should also have a minor performance gain
Related Issue(s)
Fixes #11437
☁️ Nx Cloud Report
CI is running/has finished running commands for commit c6de90b0f410eec6c1581519f03feabb744c76a0. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this branch
✅ Successfully ran 12 targets
nx affected --target=e2e --base=6b9f44f10eef9d63f2b5d3d0e1583ca4bf1c63e3 --head=c6de90b0f410eec6c1581519f03feabb744c76a0 --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox --parallel=1nx affected --target=lint --base=6b9f44f10eef9d63f2b5d3d0e1583ca4bf1c63e3 --head=c6de90b0f410eec6c1581519f03feabb744c76a0 --parallel=3nx affected --target=build --base=6b9f44f10eef9d63f2b5d3d0e1583ca4bf1c63e3 --head=c6de90b0f410eec6c1581519f03feabb744c76a0 --parallel=3nx affected --target=test --base=6b9f44f10eef9d63f2b5d3d0e1583ca4bf1c63e3 --head=c6de90b0f410eec6c1581519f03feabb744c76a0 --parallel=1nx-cloud record -- yarn nx workspace-lintnx-cloud record -- yarn documentationnx build typedoc-themenx-cloud record -- yarn depchecknx-cloud record -- yarn check-lock-filesnx-cloud record -- yarn check-commitnx-cloud record -- yarn nx format:check --base=6b9f44f10eef9d63f2b5d3d0e1583ca4bf1c63e3 --head=c6de90b0f410eec6c1581519f03feabb744c76a0nx-cloud record -- yarn check-imports
Sent with 💌 from NxCloud.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
| Name | Status | Preview | Updated |
|---|---|---|---|
| nx-dev | ⬜️ Ignored (Inspect) | Aug 15, 2022 at 0:03AM (UTC) |
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.