[ ] Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
I have created a custom ngAdd schematic, where I check a boolean option (--local), and if it is set I want to perform a link to a local package instead of the npm registry.
Command
other
Is this a regression?
The previous version in which this bug was not present was
No response
Description
I have created a custom
ngAdd
schematic, where I check a boolean option (--local
), and if it is set I want to perform a link to a local package instead of the npm registry.In order to do this, instead of:
for each package I want to link I do
However, the command fails. It seems that the actual command being ran is
npm test-package
wheretest-package
is the package I want to link.After checking the executor, it seems that the link command of
NodePackageLinkTask
is disregarded entirely: https://github.com/angular/angular-cli/blob/b4a12a9264033c18cdc2de81b05a2d1f41d549e2/packages/angular_devkit/schematics/tasks/package-manager/executor.ts#L91C9-L98Minimal Reproduction
Follow the ngAdd tutorial, and use
NodePackageLinkTask
instead of NodePackageInstallTask`.Exception or Error
Your Environment
Anything else relevant?
This does not seem to have changed in the past angular versions.