ng add --registry=<registryUrl>

[dherges]

🚀 Feature request

Command (mark with an x)

$ ng add --registry=http://localhost:4873 @foo/bar

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [x] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Description

ng update --registry=<registry> allows to update packages from private registry.

However, ng add offers no capability to add a package from a private registry. The current workaround is to manually create a .npmrc file in the CLI workspace root, adding the registry configuration there.

Describe the solution you'd like

• fetchPackageManifest and fetchPackageMetadata already have option for registry

  • angular-cli/packages/angular/cli/utilities/package-metadata.ts

    Line 210 in fedda40

    export async function fetchPackageManifest(

  • angular-cli/packages/angular/cli/utilities/package-metadata.ts

    Line 160 in fedda40

    registry?: string;

• add --registry argument to ng add command

  • angular-cli/packages/angular/cli/commands/add-impl.ts

    Line 30 in fedda40

    async run(options: AddCommandSchema & Arguments) {

• pass --registry arguments to install arguments

  • angular-cli/packages/angular/cli/tasks/npm-install.ts

    Line 56 in fedda40

    spawn(packageManager, installArgs, installOptions)

Describe alternatives you've considered

See above: .npmrc file.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}