Falls over on startup, with Error about npm-gui

[q-nick]

Hi, @jimrandell you are right. It looks like it crashes on your global dependencies.

Could you post the result of this command: npm ls --depth=0 -g --json it should display exactly what npm-gui is using here.

[jimrandell]

hi, sorry, it's a crazy busy time at work right now
(why I'm using your tool)

thank you again for your efforts with this project!

Result running command: npm ls --depth=0 -g --json

{
  "name": "npm",
  "dependencies": {
    "@babel/highlight": {
      "version": "7.14.5"
    },
    "@typescript-eslint/eslint-plugin": {
      "version": "5.14.0"
    },
    "blockly": {
      "version": "7.20211209.2"
    },
    "deuglify": {
      "version": "1.0.0"
    },
    "eslint-init": {
      "version": "0.1.12"
    },
    "etc": {},
    "fish": {
      "version": "0.0.0"
    },
    "java": {
      "version": "0.12.2"
    },
    "madge": {
      "version": "5.0.1"
    },
    "mariadb": {
      "version": "2.5.5"
    },
    "npm-cli": {
      "version": "0.1.0"
    },
    "npm": {
      "version": "7.24.0"
    },
    "nw-gyp": {
      "version": "3.6.5"
    },
    "yo": {
      "version": "4.3.0"
    }
  }
}

[GlennSandoval]

This happens for me as well, but only after updating npm via npm install npm -g.

[ealib]

Same here with 4.0.2 running with

• Windows 10 x64
• Node.js v18.13.0
• npm 9.3.1

Here one of the global dependencies is actually missing the version property.

{
  "name": "npm",
  "dependencies": {
    // ...
    "@vercel/ncc": {
      "overridden": false
    },
   // ...
  }
}

Uninstalling it and re-installing it solved the problem:

{
  "name": "npm",
  "dependencies": {
    // ...
    "@vercel/ncc": {
      "version": "0.36.0",
      "overridden": false
    },
   // ...
  }
}

[q-nick]

@ealib I just released version 4.0.3 which should cover this case. Would you like to confirm if it is better now?

npx npm-gui@latest

[ealib]

@q-nick I updated to version 4.0.3 and now to 4.0.4 and both keep working, but I don't know how to simulate the old issue with missing version property. I think, however, that if you provided in the code to handle that case, which was clearly the source of the problem, this issue could be closed.

[q-nick]

@ealib closing, thanks.