You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Upgrade Angular-CLI on Windows 10 with beta.17 fails to run #2631
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
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!
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\?
@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!!!
Activity
dzonatan commentedon Oct 10, 2016
Maybe you missed
versionproperty inangular-cli.jsonfile.It should be updated to
1.0.0-beta.14or1.0.0-beta.17as well.filipesilva commentedon 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.
lekova commentedon Oct 11, 2016
The
testfolder is empty. I tried to create new project inside it withng new test-project. Just putng -vthere to demonstrate thatngis not running. Sorry for the confusion!filipesilva commentedon Oct 14, 2016
Hm.... this error can appear if there's a
node_modulesfolder 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 commentedon 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 cleanandinstall latest. Verified withng newandng serve. Thanks!!!filipesilva commentedon Oct 17, 2016
Glad to hear it's sorted!
#2178 should have sorted this scenario overall, but if there's a older
nginstall up in the tree that one will be used instead.angular-automatic-lock-bot commentedon Sep 6, 2019
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.