feat(@angular/cli): allow using Deno as package manager

[csvn]

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: #30947

What is the new behavior?

It's possible to use deno to install packages, similar to bun.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[alan-agius4]

@csvn, can you please rebase? Thanks.

[csvn]

Sorry for the delay, rebased now @alan-agius4 🙂

[alan-agius4]

Looks like Deno has a bug. And the install is failing with Failed to parse "/package.json" as JSON. UnexpectedEndOfString at offset: 456.

[alan-agius4]

This seems to have changed.

deno --version
deno 2.5.6 (stable, release, x86_64-unknown-linux-gnu)
v8 14.0.365.5-rusty
typescript 5.9.2

[csvn]

Hmm... maybe this differs by platform? For me on Windows I get a shorter version output with -v, and a more verbose one with --version. That's why I added the ternary to switch to the -v flag on L224:

angular-cli/packages/angular/cli/src/utilities/package-manager.ts

Line 224 in 38470cb

const versionArg = name !== PackageManager.Deno ? '--version' : '-v';

> PS C:\Users\csvn\dev\angular-cli> deno --version
deno 2.5.6 (stable, release, x86_64-pc-windows-msvc)
v8 14.0.365.5-rusty
typescript 5.9.2

> PS C:\Users\csvn\dev\angular-cli> deno -v
deno 2.5.6

I used the shorter one (-v) to simplify parsing the version correctly. But I could perhaps change to a regex to extract the version when using --version? Something along the lines of /deno (?<version>\S{5,})/.

[csvn]

I haven't looked into the E2E test errors yet, so I don't know why those fail. But I know it works to create a new Angular project with Deno like this:

> PS C:\Users\ChristianSvensson\Dev\_personal> deno run -Ar npm:@angular/cli new test-project --skip-install --test-runner karma
✔ Which stylesheet system would you like to use? CSS             [ https://developer.mozilla.org/docs/Web/CSS]
✔ Do you want to enable Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering)? No
✔ Which AI tools do you want to configure with Angular best practices? https://angular.dev/ai/develop-with-ai None
CREATE test-project/angular.json (2166 bytes)
...[snip]...
CREATE test-project/public/favicon.ico (15086 bytes)
    Successfully initialized git.

> PS C:\Users\ChristianSvensson\Dev\_personal>

[alan-agius4]

Can you try to update to 2.5.6 to see if the Deno install issue has been addressed?

[csvn]

Updated in 4d0947a.

[csvn]

I missed scope in my commits, force pushed to correct commit messages and address failing lint job. 😅