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

[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

[alan-agius4]

Love the idea @brandonroberts.

[angular-robot]

This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list.

You can find more details about the feature request process in our documentation.

[brandonroberts]

Awesome!

[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.}