Skip to content
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

Upgrade Angular-CLI on Windows 10 with beta.17 fails to run #2631

Closed
lekova opened this issue Oct 10, 2016 · 7 comments
Closed

Upgrade Angular-CLI on Windows 10 with beta.17 fails to run #2631

lekova opened this issue Oct 10, 2016 · 7 comments
Labels
needs: more info Reporter must clarify the issue

Comments

@lekova
Copy link

lekova commented Oct 10, 2016

Tried to do the upgrade from beta.10 to beta.14 described in the wiki page and got a problem where the installation process is successful however I cannot run ng --version.

After couple of days I tried again (we are at beta.17) so I followed the same steps

  • node update
  • npm uninstall angular-cli -g
  • npm cache clean
  • npm install angular-cli@latest -g

I get the same problem as before:
angular-cli windows

@dzonatan
Copy link
Contributor

dzonatan commented Oct 10, 2016

Maybe you missed version property in angular-cli.json file.
It should be updated to 1.0.0-beta.14 or 1.0.0-beta.17 as well.

@filipesilva
Copy link
Contributor

filipesilva commented Oct 10, 2016

Wait, is that inside the project? Since the upgrade process requires you to make a new project, you should do it outside of the existing project.

@filipesilva filipesilva added the needs: more info Reporter must clarify the issue label Oct 10, 2016
@lekova
Copy link
Author

lekova commented Oct 11, 2016

The test folder is empty. I tried to create new project inside it with ng new test-project. Just put ng -v there to demonstrate that ng is not running. Sorry for the confusion!

@filipesilva
Copy link
Contributor

Hm.... this error can appear if there's a node_modules folder with an older version anywhere in the folder hierarchy. Do you get the same error if you do this in, say, C:\test-folder\?

@lekova
Copy link
Author

lekova commented Oct 17, 2016

@filipesilva, that is exactly the problem I had. There are projects with an older version in the folder tree where I was trying to install the latest angular-cli. So I did as you suggested, cd to C:\, uninstall, cache clean and install latest. Verified with ng new and ng serve. Thanks!!!

@filipesilva
Copy link
Contributor

filipesilva commented Oct 17, 2016

Glad to hear it's sorted!

#2178 should have sorted this scenario overall, but if there's a older ng install up in the tree that one will be used instead.

@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs: more info Reporter must clarify the issue
Projects
None yet
Development

No branches or pull requests

3 participants