Skip to content

[FEAT]: Use the appropriate package manager by default when using @angular to install #23617

@brandonroberts

Description

@brandonroberts

🚀 Feature request

Command (mark with an x)

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • extract-i18n
  • run
  • config
  • help
  • version
  • doc

Description

A clear and concise description of the problem or missing capability...

When using yarn create @angular to scaffold a new application, it still uses npm to install dependencies.

Describe the solution you'd like

If you have a solution in mind, please describe it.

When using a different package manager` to scaffold a new application, it should use the package manager used to initiate the command.

npm init @angular - npm
yarn create @angular - yarn
pnpm create @angular - pnpm (if pnpm works?)

Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?

The alternative command works

yarn create @angular -- --package-manager yarn

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions