Skip to content

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

Closed

Description

@lekova

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

Activity

  1. dzonatan commented on Oct 10, 2016

    @dzonatan
    Contributor

    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.

  2. filipesilva commented on Oct 10, 2016

    @filipesilva
    Contributor

    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.

  3. lekova commented on Oct 11, 2016

    @lekova
    Author

    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!

  4. filipesilva commented on Oct 14, 2016

    @filipesilva
    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\?

  5. lekova commented on Oct 17, 2016

    @lekova
    Author

    @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!!!

  6. filipesilva commented on Oct 17, 2016

    @filipesilva
    Contributor

    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.

  7. angular-automatic-lock-bot commented on Sep 6, 2019

    @angular-automatic-lock-bot

    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.

  8. locked and limited conversation to collaborators on Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions