Skip to content

fix: npm-resolution fixture self-conflicts on every Angular patch release #1897

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.

Sign up for GitHub

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

Merged
lskramarov merged 1 commit into from
Aug 14, 2026
+11 −3
Merged

fix: npm-resolution fixture self-conflicts on every Angular patch release #1897

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions tools/check-npm-resolution/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,13 +72,21 @@ const ngNewApp = () => ({
}
});

/** An application that already depends on the Angular packages `@koobiq/components` peers on. */
/**
* An application that already depends on the Angular packages `@koobiq/components` peers on.
*
* The two extra peers carry the same range shape as the rest of the fixture, not this repository's
* exact pins. Mixing the two makes the fixture contradict itself the moment Angular publishes a
* patch: everything inherited from `ngNewApp()` floats to the new version, while an exact
* `@angular/animations` holds `@angular/core` back — `@angular/animations@x.y.z` peers on
* `@angular/core@x.y.z` exactly — and npm fails on a conflict no `@koobiq/*` package takes part in.
*/
const angularAppWithPeers = () => ({
...ngNewApp(),
dependencies: {
...ngNewApp().dependencies,
'@angular/animations': angularVersion,
'@angular/cdk': cdkVersion
'@angular/animations': angularRange,
'@angular/cdk': ngNewRange(cdkVersion)
}
});

Expand Down