No update check for global packages

[jerone]

When opening npm-gui with global packages, the update check doesn't return anything:

There should be updates for:

• @angular/cli 15.0.5 → 15.1.1
• npm 9.2.0 → 9.3.0

---

npm-gui version 4.0.1

[q-nick]

Hi @jerone, unfortunately, I can't find any cause for that.

Would you like to share the output of a few additional commands, I need:

npm ls -g --depth=0 --json - will list all your globally installed packages and installed versions

npm outdated -g --json - will show all the latest versions of your global packages - probably this command is somehow broken.

[jerone]

This is the log from npm-gui:

OK: npm ls -g --depth=0 --json
Command: npm --version, started
Command: npm ls -g --depth=0 --json, started
Command: yarn --version, started
Command: pnpm --version, started
OK: npm ls -g --depth=0 --json
Command: npm outdated -g --json, started
OK: npm outdated -g --json

This is from npm ls -g --depth=0 --json:

{
  "resolved": "file:../Users/<user>/AppData/Roaming/nvm/v18.11.0",
  "dependencies": {
    "@angular/cli": {
      "version": "15.0.5",
      "overridden": false
    },
    "@cspell/dict-nl-nl": {
      "version": "2.2.8",
      "overridden": false
    },
    "corepack": {
      "version": "0.15.3",
      "overridden": false
    },
    "cspell": {
      "version": "6.18.1",
      "overridden": false
    },
    "generator-code": {
      "version": "1.7.2",
      "overridden": false
    },
    "generator-eslint": {
      "version": "4.1.1",
      "overridden": false
    },
    "generator-jest": {
      "version": "1.8.0",
      "overridden": false
    },
    "generator-sublime": {
      "version": "2.0.13",
      "overridden": false
    },
    "js-to-ts-converter": {
      "version": "0.18.2",
      "overridden": false
    },
    "np": {
      "version": "7.6.3",
      "overridden": false
    },
    "npm-check-updates": {
      "version": "16.6.2",
      "overridden": false
    },
    "npm-gui": {
      "version": "4.0.3",
      "overridden": false
    },
    "npm": {
      "version": "9.2.0",
      "overridden": false
    },
    "web-ext": {
      "version": "7.4.0",
      "overridden": false
    },
    "yarn": {
      "version": "1.22.19",
      "overridden": false
    },
    "yo": {
      "version": "4.3.1",
      "overridden": false
    }
  }
}

This is from npm outdated -g --json:

{}

[jerone]

npm-check-updates however, is correctly detecting outdated packages:

 @angular/cli       15.0.5  →  15.1.2
 cspell             6.18.1  →  6.19.2
 npm                 9.2.0  →   9.3.1
 npm-check-updates  16.6.2  →  16.6.3
 web-ext             7.4.0  →   7.5.0

[jerone]

There are similar issues reported:

• [BUG] npm outdated does not list global installed packages npm/cli#6098
• [BUG] npm outdated -g not work npm/cli#5182

The last issue mentions the use of nvm, which uses symlink for using the right node.js (and unassumingly also global packages). I'm using https://github.com/coreybutler/nvm-windows/

This also corresponds to this old issue: npm/npm#9564

But then again, npm-check-updates does detect updates correctly.

[q-nick]

@jerone I got some idea.

Could you check if you have the newest version under the black button (the one with "=>" mark)?

[q-nick]

[jerone]

[jerone]

Weirdly enough, the following command does check for outdated packages and comes back with an huge list of outdated package.
But the list contains the dependencies of dependencies (because that's what --all does):

npm outdated -g --all

Sadly npm outdated -g --all --depth=0 did not change the huge list.

The more I think about this, the more I'm convinced this is an NPM issue.
But I was wondering how your output of npm outdated -g --json looks like...

[q-nick]

Great research @jerone !
I will provide, a unique workaround for global dependencies update - based on versions in package details.

Many thanks!

[q-nick]

@jerone Hi, I released version 4.0.5-beta-1 which should contain a fix for this problem.

Would you like to confirm?

npx [email protected]

[jerone]

Hi @q-nick, I tried it just now, and this is the result:

According to ncu I should see two outdated global packages:

PS C:\Users\jerone> ncu -g
[====================] 17/17 100%

 cspell  6.23.0  →  6.26.1
 npm      9.4.2  →   9.5.0

Here is the log from the console when running npx [email protected]...

PS C:\Users\jerone> npx [email protected]
Need to install the following packages:
  [email protected]
Ok to proceed? (y)
listening on: localhost 13377
Command: npm ls -g --depth=0 --json, started
ERROR HANDLER Error: invalid project structure!
    at Object.callback (C:\Users\jerone\AppData\Local\npm-cache\_npx\cb45cb7a4356409f\node_modules\npm-gui\dist\server\index.js:1:10548)
    at K.onIncomingMessage (C:\Users\jerone\AppData\Local\npm-cache\_npx\cb45cb7a4356409f\node_modules\npm-gui\dist\server\index.js:1:9072)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
OK: npm ls -g --depth=0 --json
Command: npm --version, started
Command: npm ls -g --depth=0 --json, started
Command: npm info @angular/[email protected] --json, started
Command: npm info @cspell/[email protected] --json, started
Command: npm info @vscode/[email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: yarn --version, started
OK: npm info [email protected] --json
OK: npm info @angular/[email protected] --json
OK: npm info [email protected] --json
OK: npm info [email protected] --json
OK: npm info [email protected] --json
OK: npm info @cspell/[email protected] --json
OK: npm info [email protected] --json
OK: npm info [email protected] --json
OK: npm info [email protected] --json
OK: npm info @vscode/[email protected] --json
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: npm info [email protected] --json, started
Command: pnpm --version, started
OK: npm info [email protected] --json
OK: npm info [email protected] --json
OK: npm info [email protected] --json
OK: npm info [email protected] --json
OK: npm info [email protected] --json
OK: npm info [email protected] --json
OK: npm ls -g --depth=0 --json
Command: npm outdated -g --json, started
OK: npm info [email protected] --json
OK: npm outdated -g --json

The error at the beginning is correct because I started the tool on an not-project folder.