Skip to content

Angular CLI should require at least node v6.x.x and npm 3.x.x #1046

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hacknaked opened this issue Jun 9, 2016 · 7 comments
Closed

Angular CLI should require at least node v6.x.x and npm 3.x.x #1046

hacknaked opened this issue Jun 9, 2016 · 7 comments
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent type: bug/fix

Comments

@hacknaked
Copy link

hacknaked commented Jun 9, 2016

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.

@hacknaked hacknaked changed the title Angular CLI should require node v5.x.x and npm 3.x.x Angular CLI should require at least node v5.x.x and npm 3.x.x Jun 9, 2016
@BernhardRode
Copy link

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.

@kylecordes
Copy link

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.

@filipesilva filipesilva added type: bug/fix P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Jun 15, 2016
@hacknaked
Copy link
Author

hacknaked commented Jun 16, 2016

Related: #1110 #1097

@hacknaked hacknaked changed the title Angular CLI should require at least node v5.x.x and npm 3.x.x Angular CLI should require at least node v6.x.x and npm 3.x.x Jun 16, 2016
@filipesilva
Copy link
Contributor

We're now also testing on Node 6 with ce8d020, but for now will not enforce using node 6.

@arlowhite
Copy link

README.md still says:

The generated project has dependencies that require Node 4.x.x and NPM 3.x.x.

Also, I would link users to NVM as a solution for switching between Node versions.

Something like:
"If your projects require different Node versions, you may want to use Node Version Manager"

@shidhu40
Copy link

shidhu40 commented Mar 7, 2019

NPM Version: 6.7.0
Node Version: v11.10.1

When I execute command npm install -g @angular/cli

Installation gets stuck during execution . Stucked on [email protected]

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent type: bug/fix
Projects
None yet
Development

No branches or pull requests

6 participants