-
Notifications
You must be signed in to change notification settings - Fork 12k
fix(@angular/cli): direct Angular schematic dependency requests to known versions #19857
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
Conversation
b30210e
to
15a92ab
Compare
2113c81
to
451cc8a
Compare
…kflow engine host This adds an option to the NodeWorkflow to allow a custom NodeModulesEngineHost to be used with the workflow.
…known versions This change adds logic to redirect module resolution requests for Angular schematics to ensure that the correct versions of core schematic related packages are used. This also ensures that the runtime version of the schematics package matches the version used inside the schematic and that object instances passed into the schematic are compatible. The current set of core schematic related packages are `@angular-devkit/*` and `@schematics/angular`. Only first-party Angular schematics are currently affected by this change.
451cc8a
to
a2caf64
Compare
/** | ||
* Minimal shim modules for legacy deep imports of `@schematics/angular` | ||
*/ | ||
const legacyModules: Record<string, unknown> = { |
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.
Good call to add a shim
Thank you! |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This change adds logic to redirect module resolution requests for Angular schematics to ensure that the correct versions of core schematic related packages are used. This also ensures that the runtime version of the schematics package matches the version used inside the schematic and that object instances passed into the schematic are compatible.
The current set of core schematic related packages are
@angular-devkit/*
and@schematics/angular
. Only first-party Angular schematics are currently affected by this change.This change also solves issues such as #16392 which were caused by the package manager not hoisting the core schematic packages to a location the update migrations could access.