-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(angular): add check before attempting to collect secondary entrypoints #11437 #11496
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
09a3f2c
to
ee97efd
Compare
const tsConfigAliasesForLibWithSecondaryEntryPoints = Object.entries( | ||
tsconfigPathAliases | ||
).reduce((acc, [tsKey, tsPaths]) => { | ||
if (!tsKey.startsWith(library.importKey)) { | ||
return { ...acc }; | ||
} | ||
|
||
if (tsPaths.some((path) => path.startsWith(`${library.root}/`))) { | ||
acc = { ...acc, [tsKey]: tsPaths }; | ||
} | ||
|
||
return acc; | ||
}, {}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's already some sort of filtering inside collectWorkspaceLibrarySecondaryEntryPoints
which becomes useless with this change. I think it would be better to move this filter inside that function and replace the old filter that's there. Wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I think that makes sense, I updated it
ee97efd
to
6b93fc8
Compare
6b93fc8
to
c486293
Compare
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. |
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