We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
new
I cannot see that schematics cli commands added to the command select options.
When you create a new schematic project you only have the ability to specify the name and the author. However, you cannot specify the package manager.
The NodePackageInstallTask already allows the package manager option. To support the package manager option we need to do:
NodePackageInstallTask
We need to modify the factory: https://github.com/angular/angular-cli/blob/main/packages/angular_devkit/schematics_cli/blank/factory.ts in the line 93, we need to add the package manager option.
We need to add the input to the schema.json: https://github.com/angular/angular-cli/blob/main/packages/angular_devkit/schematics_cli/blank/schema.json
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Command
new
Description
I cannot see that schematics cli commands added to the command select options.
When you create a new schematic project you only have the ability to specify the name and the author. However, you cannot specify the package manager.
Describe the solution you'd like
The
NodePackageInstallTask
already allows the package manager option. To support the package manager option we need to do:We need to modify the factory: https://github.com/angular/angular-cli/blob/main/packages/angular_devkit/schematics_cli/blank/factory.ts in the line 93, we need to add the package manager option.
We need to add the input to the schema.json: https://github.com/angular/angular-cli/blob/main/packages/angular_devkit/schematics_cli/blank/schema.json
Describe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: