Angular CLI, Angular, Node.js, TypeScript, and RxJS compatibility matrix. Based on changelogs, metadata, and hands-on experience. Major versions above officially supported versions are not listed. Note that minor TypeScript versions also contain breaking changes.

angular-cli-node-js-typescript-rxjs-compatiblity-matrix.csv

Thank you

Thanks a lot!

Thanks!

Thanks for your kind words 😊 Support and encouragement matter!

Your work matters too :)

Very useful.

Thanks!

Nice done @LayZeeDK
Tks a million

Thanks, Very useful!

Very well done!
I come here regularly and I appreciate your excellent work.
Thank you for the regular updates!

Thanks !

❤️

Can I ask for the basis of this table please, that would help me out a lot, thanks!

Hi @neil-borbon,

As mentioned in the description, this information is based on changelogs, metadata, and hands-on experience.

What does this refer to: 10.13.x/12.11.x? Is it either one of the two? I am uncertain.

Hi @troelsbentsen,

It refers to support for both 10.x and 12.x major versions of Node.js with that version of Angular but officially they have to be at least 10.13.0 or 12.11.0.

Thank you!

This is awesome! Something the Angular team should do themselves :-)

This is really cool. Thanks for all this cumulative information. I hope Angular team adds something like this to their documentation some day.

Thanks for this!

Thanks for this very helpful information. I have a serious problem now and maybe someone can help with this? I have an Angular 10 & Ionic 5 project which requires NPM 7.x. So I've installed Node 15.x. Now I have a new project with Angular 12 which I cannot setup due to the error message "The engine 'node' is incompatible with this module."

I searched a bit and found this:

• Angular 11 (and lower): "Angular requires a current, active LTS, or maintenance LTS version of Node.js." (https://v11.angular.io/guide/setup-local)
• Angular 12: "Angular requires an active LTS or maintenance LTS version of Node.js." (https://angular.io/guide/setup-local)

Does anyone here know why Angular 12 stops supporting a current Node.js version?

Hi @mfrieling,

Does anyone here know why Angular 12 stops supporting a current Node.js version?

I'm not quite sure why Node 15x is not yet supported. I have worked around the problem by using nodist (alternatives are available as well) to manage my node & npm versions. It enables one to set a global and a local version of node/npm. For example, I am running node 15.x globally, but my Angular 12 project is set to use local node version 14.17.0:

I mention this just in case it is helpful for you too... :)

Hi @WinthorpeCross,
Node 15.x will never be supported as far as I understand the Node.js release policy:

After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use.
https://nodejs.org/en/about/releases/

But 16.x is the current version from April 20th 2021 till Oct 26th 2021 and thus should be supported. At least I couldn't find any information why Angular 12 stops supporting the current version and only supports the active LTS and maintenance LTS version.

But I managed to install Node 14 (including NPM 6) and then updating NPM to 7 and get both projects working with this combination.

As per the compatibility matrix, Angular started supporting Node.js 14.x in Angular 12.0 and removed support for Node.js 10.x but continues to support Node.js 12.x. Angular doesn't officially support Node.js 16.x.

As mentioned by one of you, the Node.js odd version major releases (11.x, 13.x, 15.x) are experimental and should be considered unstable. The Node.js even major releases (12.x, 14.x, 16.x) are stable LTS releases until replaced by a newer version.

NPM is independently updatable but might not support all Node.js major versions.

I use Volta to lock the Node.js version per project.

But 16.x is the current version from April 20th 2021 till Oct 26th 2021 and thus should be supported. At least I couldn't find any information why Angular 12 stops supporting the current version and only supports the active LTS and maintenance LTS version.

This must have been a misprint:

Angular 11 (and lower): "Angular requires a current, active LTS, or maintenance LTS version of Node.js."

Angular never officially supported current Node.js releases (the odd major version releases).

I don't why its not working. My config:
typescript: 4.1.5
nodejs: 12.11.0
amgular 11.2.13

@aps08
Please try Node.js version 12.22.1.

thank you, while updating the package in angular and node it's really cool help to manage.. TypeScript Dependency

Good job , Thanks !

In angular 2's docs, it says there you can install angular-cli though.

https://v2.angular.io/docs/ts/latest/cli-quickstart.html

Hi @neil-borbon,

I added the prerelease Angular CLI versions built for the Angular 2.x versions.

Excellent! Very useful information! Thanks

angular 12.x actually requires nodejs v12.14.1 or above or nodejs 14.0.0 or above. refer engines here. also, the typescript version required is >=4.2.3 but <4.3.x, which is actually only 2 versions available today, 4.2.3 and 4.2.4. check about that here.

Thanks for the update, @ninjabhishek 🤝

You're right about Node.js 12.14.x and I changed the matrix accordingly. By the way, refer to the engines metadata for the @angular/cli property as it has had that metadata for a long time whereas the @angular/core package has just now gotten it.

About Node.js 14.x, I list 14.15.x because that was the first LTS (stable) version of Node.js 14.x. I don't care what Angular's metadata says 😅

if you are constantly changing version of node and angular then you also need to keep your eye on the version of npm you are having.
The version of npm also matters. Sometimes you need to downgrade your npm version.
error would look like: css@loader error or css-loader error

@LayZeeDK, then it seems to be a quite persistent misprint.

This must have been a misprint:

Angular 11 (and lower): "Angular requires a current, active LTS, or maintenance LTS version of Node.js."

Angular never officially supported current Node.js releases (the odd major version releases).

The sentence

Angular requires a current, active LTS, or maintenance LTS version of Node.js.

can be found on setup local development guides for

• Angular 9
• Angular 10
• Angular 11

And I'm not talking about the odd major version releases here but the even ones which later will become active and LTS only.

That's right, @aps08. I was looking into this recently when I figured out the compatibility entries for Angular 2.x. We could consider an additional column for this. Until then, I recommend Volta. It's good at seamlessly switching Node.js and NPM versions on a per-project basis.

@mfrieling

Angular has both historically and to this day only added support for new major versions of Node.js after they went LTS so I don't see a good reason to list pre-LTS versions of Node.js. Let me know if you spot a good reason.

Personally, I have experienced issues with trying to use Current Node.js versions before official support has been added to Angular.

@LayZeeDK, I totally understand this. But I don't understand why the official documentation for Angular 9 to 11 says sth. different then.

Thanks for this!

But the thing I really want--and I know this is a lot to ask--is a list of the dependencies that should not be updated to their latest version for a given package. For instance, should I update to RxJS7 or not right now? It wouldn't break my code...the unanswered question is, would it break Angular in its latest stable release? Yes/no/who knows?

It should be a standard that known breaking updates are listed for every github package so we know what not to update and don't waste time re-testing facts the committers already are aware of. Thanks!

@spicemix
You can figure this out by reading the package.json files of the Angular packages. For example, at the time of writing, this is the content of @angular/core's package.json file:

{
  "name": "@angular/core",
  "version": "12.1.2",
  "description": "Angular - the core framework",
  "author": "angular",
  "license": "MIT",
  "engines": {
    "node": "^12.14.1 || >=14.0.0"
  },
  "dependencies": {
    "tslib": "^2.2.0"
  },
  "peerDependencies": {
    "rxjs": "^6.5.3",
    "zone.js": "~0.11.4"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/angular/angular.git",
    "directory": "packages/core"
  },
  "ng-update": {
    "migrations": "./schematics/migrations.json",
    "packageGroup": [
      "@angular/core",
      "@angular/bazel",
      "@angular/common",
      "@angular/compiler",
      "@angular/compiler-cli",
      "@angular/animations",
      "@angular/elements",
      "@angular/platform-browser",
      "@angular/platform-browser-dynamic",
      "@angular/forms",
      "@angular/platform-server",
      "@angular/upgrade",
      "@angular/router",
      "@angular/language-service",
      "@angular/localize",
      "@angular/service-worker"
    ]
  },
  "sideEffects": false,
  "main": "./bundles/core.umd.js",
  "fesm2015": "./fesm2015/core.js",
  "esm2015": "./esm2015/core.js",
  "typings": "./core.d.ts",
  "module": "./fesm2015/core.js",
  "es2015": "./fesm2015/core.js"
}

(As seen at https://cdn.jsdelivr.net/npm/@angular/core/package.json)

We see that Angular 12.1.x has 3 external dependencies:

• tslib supporting versions greater than or equal to 2.2.0 but below 3.0.0
• rxjs supporting versions greater than or equal to 6.5.3 but below 7.0.0
• zone.js supporting versions greater than or equal to 0.11.4 but below 0.12.0

If we upgrade these packages to versions beyond what is listed as officially supported by Angular, we are on our own.

I should have included in my comment that I understand package.json can (and once in a while, actually does) specify upgrade ranges. However, it's already known, judging from github comments, that RxJS7 works with Angular 12, but since it would potentially break user code, they won't up that designation until Angular 13.

What I want, specifically, is a summary of the best experience as reflected in test suites, effective user reports, developer understanding. If it's in package.json it will be automatically upgraded by npm/yarn. So it can't be there, but the knowledge is out there, presently difficult to mine out of stacks of github issues etc. Isn't this all about avoiding having to repeat work?

very helpful

Awesome

@spicemix
I don't think we should list major versions that are not officially supported by Angular. This guide does not try to list dependency combinations that are technically compatible. That's for projects to explore on their own.

I have added officially compatible RxJS versions.

I have added officially compatible RxJS versions.

Very useful information as well. Thanks!

Nodejs 14.17 not supported ? Currently running Angular with Node v14.17.0 and it works

@Yohandah

14.15.x or later minor version

This means 14.15.x, 14.16.x, 14.17.x are all officially supported but not 14.14.x and lower. They might work though.

Angular 12.2 now officially has opt-in support for RxJS 7.

For Node.js support, see:

• https://github.com/angular/angular-cli/blob/master/packages/angular/cli/bin/ng.js
• https://github.com/angular/angular-cli/blob/master/lib/packages.ts
• https://github.com/angular/angular-cli/blob/master/package.json

How about, can anybody help me to find the similar compatible version for Angular 1.4.5 and its compatibility with Node (&npm) ?
I, in fact, search the most possible places.
Really appreciate the help.

Great work, highly appreciate this information 🙂

@RiteshAryal if you look at AngularJS version 1.4.5's package.json file, it claims that it supports Node.js 0.10.x and npm 2.5.x:

https://github.com/angular/angular.js/blob/v1.4.5/package.json#L10-L13