Support for Deno 2.0 in Angular

[nikl0n]

Which @angular/* package(s) are relevant/related to the feature request?

core

Description

With the release of Deno 2.0, compatibility with Node.js and npm has been significantly enhanced, allowing frameworks like Angular to operate within the Deno environment. Integrating Angular with Deno 2.0 would provide developers with a modern, secure, and efficient runtime for building Angular applications.

Proposed solution

• Update the Angular CLI to support Deno 2.0 for project scaffolding, building, and serving applications.
• Ensure that @angular/core and related packages are compatible with Deno's module system and runtime APIs.
• Provide documentation and examples demonstrating how to develop, build, and deploy Angular applications using Deno 2.0.

Implementing these changes would expand Angular's versatility and offer developers more choices in their development environments.

Alternatives considered

Before proposing official support for Deno 2.0 in Angular, I explored the following alternatives:

1. Manual Configuration: Attempted to manually configure Angular projects to run on Deno by adjusting build scripts and dependencies. However, this approach proved complex and error-prone, leading to maintenance challenges.
2. Community Plugins: Searched for community-developed plugins or tools that facilitate Angular's integration with Deno. While some experimental solutions exist, they lack comprehensive support and are not actively maintained.
3. Alternative Frameworks: Considered using other frameworks that natively support Deno. However, this would require significant refactoring of existing Angular applications and retraining of development teams.

These alternatives highlighted the need for official support to ensure a seamless and reliable integration of Angular with Deno 2.0.

[clydin]

Since Deno 2.0 is intended to be fully compatible with both Node.js and npm, Angular should work without any special instructions. Angular can currently be used with a variety of Node package managers such as npm, pnpm, yarn, or any other by skipping the install on project creation. Just as with these package managers, it should also be able to be used with Deno or Bun assuming that these runtimes provide compatibility as documented. If differences arise where Angular works within Node.js but not Deno or Bun then an issue should ideally be created with the respective runtime so that the runtimes can improve their compatibility with Node.js.

[dgp1130]

I'll also point out that Angular SSR is already compatible with Deno and other non-Node JS runtimes. We're working to make that experience even better with each release. The CLI doesn't explicitly support Deno, but like @clydin mentioned, any issues there are compatibility issues with those runners moreso than bugs in Angular CLI.

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