Skip to content

ng version display beta.21 despite .26 is installed on win7-x64 #4131

Closed

Description

@psaussure

Type

Bug, not blocking

Summary

Version displayed using ng --version on win7-x64 is wrong.

OS

Windows 7

Versions.

angular-cli: 1.0.0-beta.21
node: 7.4.0
os: win32 x64

Repro steps.

  • Installed clean node
  • Check no global node_modules is here except npm
  • npm install -g npm to update NPM
  • npm install -g angular-cli: installs the angular-cli

+-- angular-cli@1.0.0-beta.26
| +-- @angular-cli/ast-tools@1.0.15
| | -- @angular/tsc-wrapped@0.5.1 | | -- tsickle@0.2.4
| | `-- source-map-support@0.4.10
| +-- @angular-cli/base-href-webpack@1.0.15
...

  • ng --version:

angular-cli: 1.0.0-beta.21
node: 7.4.0
os: win32 x64

Additional comment

Was tested under linux and max, I don't encounter the problem and proper version is displayed.

Activity

  1. RicardoVaranda commented on Jan 20, 2017

    @RicardoVaranda
    Contributor

    @psaussure Try to clear your cache before re-installing angular-cli:

    npm uninstall -g angular-cli
    npm cache clean
    npm install -g angular-cli@latest
    
  2. Brocco commented on Jan 20, 2017

    @Brocco
    Contributor

    This could also be an issue with the local project's version of angular-cli. The global install hands off to the local installation within projects.

    So ensure that if you are in a project directory that you update that version as well.

  3. psaussure commented on Jan 20, 2017

    @psaussure
    Author

    I'm outside of any project (C: root).

    npm uninstall -g angular-cli
    npm cache clean
    npm install -g angular-cli@latest
    

    The same result occurs:

    ng --version
    angular-cli: 1.0.0-beta.21
    node: 7.4.0
    os: win32 x64
    

    I tried to remove AppData node_modules completely and rerun the sequence, still the same result.

  4. filipesilva commented on Jan 24, 2017

    @filipesilva
    Contributor

    You probably have another set of global node_modules somewhere. This can happen especially if you're using nvm. These problems are often very hard to diagnose, and completely outside the purview of the CLI.

    My best advice is to reinstall NPM (and NVM if you use it). You can also try to manually track down this second global node_modules location and fix it.

  5. psaussure commented on Jan 24, 2017

    @psaussure
    Author

    Thanks, will check on this.

  6. 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.

  7. 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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions