Are you working with Angular and need to set up projects with different Angular versions? Here’s a simple guide to creating Angular projects for specific versions, both with and without the Angular CLI!

Why Use Specific Angular Versions?

When working on multiple Angular projects, sometimes you need to lock in a particular version. Perhaps your project relies on certain features available only in specific versions, or maybe it requires compatibility with legacy codebases.

Here's how to create projects with particular Angular versions—whether or not you’re using the CLI!

1. Creating an Angular Project Without Installing the Angular CLI

Did you know that you can initialize Angular projects for specific versions without installing the CLI? Let’s look at the syntax and examples.

Syntax

npm init @angular@<version> <project-name>

Replace <version> with your desired Angular version and <project-name> with your project’s name. For instance, if you want to create an Angular 16 project named sampleApp, you’d run:

Example

npm init @angular@16 sampleApp

This approach sets up a basic Angular project without installing the Angular CLI globally. It’s handy if you want to avoid installing extra tools or if you’re working in a constrained environment.

Other Examples

• Angular 13 project named legacyApp:
  

  npm init @angular@13 legacyApp
  

This command pulls down the necessary Angular version directly, setting up the project structure and dependencies specific to that version.

2. Creating a Specific Version of an Angular Project With Angular CLI

If you prefer using the Angular CLI, you can still create a project for a specific version without permanently installing the CLI. Use npx to run the CLI directly, specifying your version.

Syntax

npx -p @angular/cli@<version> ng new <project-name>

This command uses npx to temporarily run the specified CLI version, creating a project tailored to that Angular version.

Example

npx -p @angular/cli@13 ng new demoApp

This command creates a new project using Angular CLI version 13, even if you have a different Angular CLI version installed globally.

Advantages of Using npx:

• No Permanent Installation: The specified CLI version is downloaded for one-time use, saving space and avoiding potential version conflicts.
• Easily Switch Versions: You can quickly switch between versions for different projects without managing multiple global CLI installs.

When to Choose CLI vs. Non-CLI Approaches

Without CLI

• When you want a minimal setup
• When working in a restricted environment without a global Angular CLI installation

With CLI

• When you need to leverage CLI commands and schematics
• When setting up a full-featured Angular workspace

Wrapping Up

Whether you choose to go with or without the CLI, Angular’s flexibility with npm init and npx makes it easy to manage projects across different versions. So next time you need to spin up a specific Angular version project, you’ll know exactly how to do it without needing to fuss over CLI installations!

Quick Commands Recap

And that's it! Hope you found this guide helpful for your Angular projects. Comment below with any questions or tips you might have for working with specific Angular versions.

Happy coding!