Skip to content

4.2.2 Argon MSI for 64 bit contains faulty npm version #332

@dotnetCarpenter

Description

@dotnetCarpenter

When I download the .msi installer from the nodejs front-page, I get npm version 2.12.0 which has a known issue with calling process.getuid on windows. This virtually makes npm useless hence making the Argon release useless on windows.

On the Argon changelog it says:

npm: Upgraded to npm 2.14.7 from 2.14.4, see release notes for full details (Kat Marchán) #3299

Which leads me to believe that the node-v4.2.2-x64.msi itself is packaged wrong.

Step to reproduce

  1. Download v4.2.2 LTS
  2. Install
  3. node -v v4.2.2 npm -v 2.12.0
  4. npm outdated -g
PS C:\Windows\system32> npm outdated -g
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\dotnet\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "outdated" "-g"
npm ERR! node v4.2.2
npm ERR! npm  v2.12.0

npm ERR! process.getuid is not a function
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\dotnet\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "outdated" "-g"
npm ERR! node v4.2.2
npm ERR! npm  v2.12.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions