Angular-cli: Angular CLI should require at least node v6.x.x and npm 3.x.x

Created on 9 Jun 2016 · 7Comments · Source: angular/angular-cli

I was playing with Angular CLI and I love it. Superb tool that save me a lot of time specially with all those new features of Angular 2. The only problem I had was with Node. According to docs, Angular CLI requieres Node 4 or greater, but if you are using Node 4.x and start a new project, it will fail with cryptic error messages in the browser console log.

After many hours of frustration, I realize that Angular 2 requires Node 5.x or higher:

Verify that you are running at least node v5.x.x and npm 3.x.x by running node -v and npm -v in a terminal/console window. Older versions produce errors.

By doing some research in Stack Overflow, seems that many other have faced the same problem. Look, for example, the comments in this blogpost. So, I'd like to recommend update your Prerequisites Docs to node v5.x.x and npm 3.x.x or higher in order to save hours of frustration to new people who wants to try Angular 2.

Thanks.

EDIT Jun 16

I agree with @BernhardRode and @kylecordes, Angular CLI should focus on Node 6. Please, upgrade your Prerequisites Docs to node v6.x.x and npm 3.x.x or higher, it's just a minute and will avoid lot of bug reports.

2 (required) bufix

Source

hacknaked

Most helpful comment

I'd say focus on 6, as it is going to be the next LTS. So when the CLI comes to live, we will have a solid basement.

BernhardRode on 9 Jun 2016

👍4

All 7 comments

I'd say focus on 6, as it is going to be the next LTS. So when the CLI comes to live, we will have a solid basement.

BernhardRode on 9 Jun 2016

👍4

I think the comment about version 6 is right on. There are already so many ways for CLI to explode in scope. Anywhere we can limit the scope (like chopping out old node versions) will help the team focus on making it actually work great for current versions.