npm latest version displayed is wrong

[GPT]

Bug description
npm installed version is 7.0.3 but the latest one that luna displays is 6.14.8.

To Reproduce
Just install the latest deb package: luna_3.3.5_amd64.deb

Expected behavior
To find the correct latest version of npm package which is 7.0.5 or at least 7.0.4.

Screenshots

Desktop

• OS: LinuxMint
• Version: 20

Additional context
None

[rvpanoz]

Hey @GHNewbiee! Thank you for your comment.

Could you please install the latest version and tell me if the error still occurs?
v.3.4.5

[GPT]

Yes, unfortunately, the error does still occur.

[rvpanoz]

ok I will try to reproduce it then. I will keep you updated.

[GPT]

Just keep in mind that npm shows the old version 6.14.8 different than that in @npm/cli. I suspect you retrieve package info by two different methods. The method by which you get the package versions seems more accurate and reliable, at least in the case of the npm package.

[rvpanoz]

Hey! Are you using nvm? Luna uses npm list -g --json --depth=0 and npm outdated -g --json --depth=0 commands to get the global packages and outdated packages. Could you please run npm outdated -g --json --depth=0 at the terminal and check what is the output?

[GPT]

Hi!

• No, I do not use nvm.
• npm list -g --json --depth=0 output

{
  "dependencies": {
    "csso-cli": {
      "version": "3.0.0",
      "resolved": "https://registry.npmjs.org/csso-cli/-/csso-cli-3.0.0.tgz"
    },
    "degit": {
      "version": "2.8.0",
      "resolved": "https://registry.npmjs.org/degit/-/degit-2.8.0.tgz"
    },
    "express-gateway": {
      "version": "1.16.10",
      "resolved": "https://registry.npmjs.org/express-gateway/-/express-gateway-1.16.10.tgz"
    },
    "fkill-cli": {
      "version": "6.0.1",
      "resolved": "https://registry.npmjs.org/fkill-cli/-/fkill-cli-6.0.1.tgz"
    },
    "generator-open-wc": {
      "version": "0.7.3",
      "resolved": "https://registry.npmjs.org/generator-open-wc/-/generator-open-wc-0.7.3.tgz"
    },
    "moleculer-cli": {
      "version": "0.7.1",
      "resolved": "https://registry.npmjs.org/moleculer-cli/-/moleculer-cli-0.7.1.tgz"
    },
    "moleculer-repl": {
      "version": "0.6.4",
      "resolved": "https://registry.npmjs.org/moleculer-repl/-/moleculer-repl-0.6.4.tgz"
    },
    "npm-check-updates": {
      "version": "9.2.3"
    },
    "npm-check": {
      "version": "5.9.2",
      "resolved": "https://registry.npmjs.org/npm-check/-/npm-check-5.9.2.tgz"
    },
    "npm-install-peers": {
      "version": "1.2.1",
      "resolved": "https://registry.npmjs.org/npm-install-peers/-/npm-install-peers-1.2.1.tgz"
    },
    "npm": {
      "version": "7.0.3"
    },
    "pm2": {
      "version": "4.5.0",
      "resolved": "https://registry.npmjs.org/pm2/-/pm2-4.5.0.tgz"
    },
    "web-component-analyzer": {
      "version": "1.1.6",
      "resolved": "https://registry.npmjs.org/web-component-analyzer/-/web-component-analyzer-1.1.6.tgz"
    },
    "yo": {
      "version": "3.1.1",
      "resolved": "https://registry.npmjs.org/yo/-/yo-3.1.1.tgz"
    }
  }
}

• npm outdated -g --json --depth=0 output

{
  "npm": {
    "current": "7.0.3",
    "wanted": "6.14.8",
    "latest": "6.14.8",
    "dependent": "global",
    "location": "/usr/lib/node_modules/npm"
  }
}

But I use sudo npm-check -gu

$ sudo npm-check -gu
The global path you are searching is: /usr/lib/node_modules
❤️  Your modules look amazing. Keep up the great work. ❤️

and npm-check-updates

$ npm-check-updates -g
[====================] 14/14 100%

All global packages are up-to-date :)

• finally

$ node -v
v15.0.1

Q1: Which method/package do you use to get the package versions?

[rvpanoz]

I am not using any package or a custom method to get the versions. I am using npm list and outdated commands and parsing the output.

[rvpanoz]

Note that npm v.7.x.x is a development release and thats why is not listed as LTS release which currently is 6.14.8.

[GPT]

So, it has to do with npm weird concepts. Thanks for your time!