[BUG] all commands fail: `TypeError: LRU is not a constructor`

[iambumblehead]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

npm --version and other commands print a runtime error

$ npm --version
/usr/lib/node_modules/npm/lib/es6/validate-engines.js:31
 throw err
 ^

TypeError: LRU is not a constructor
 at Object.<anonymous> (/usr/lib/node_modules/npm/node_modules/semver/classes/range.js:188:15)
 at Module._compile (node:internal/modules/cjs/loader:1241:14)
 at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
 at Module.load (node:internal/modules/cjs/loader:1091:32)
 at Module._load (node:internal/modules/cjs/loader:938:12)
 at Module.require (node:internal/modules/cjs/loader:1115:19)
 at require (node:internal/modules/helpers:130:18)
 at Object.<anonymous> (/usr/lib/node_modules/npm/node_modules/semver/functions/satisfies.js:1:15)
 at Module._compile (node:internal/modules/cjs/loader:1241:14)
 at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)

Expected Behavior

npm commands should not fail with a runtime error

$ npm --version
10.0.0-1

Steps To Reproduce

1. install npm
2. use any npm command, such as "npm --version", "npm install" or "npm test".
3. see runtime error

Environment

• npm: 10.0.0-1
• Node.js: v20.6.0
• OS Name: Arch Linux
• System Model Name: xps13
• npm config: (generated from the previous, working version of npm, version 9.8.1)

; "user" config from /home/bumble/.npmrc

//registry.npmjs.org/:_authToken = (protected) 

; node bin location = /usr/bin/node
; node version = v20.6.0
; npm local prefix = /home/bumble/software/esmock
; npm version = 9.8.1
; cwd = /home/bumble/software/esmock
; HOME = /home/bumble
; Run `npm config ls -l` to show all defaults.

[lukekarrys]

Can you try npm@10.1.0 which is the latest versions? Also how did you download this version of npm? 10.0.0-1 isn't a valid version of npm in the registry:

npm view npm --json versions
[
 ...
 "10.0.0-pre.0",
 "10.0.0-pre.1",
 "10.0.0",
 "10.1.0"
]

[iambumblehead]

@lukekarrys thank you and my apology for opening this issue here. This should have been opened at the arch package location instead https://gitlab.archlinux.org/archlinux/packaging/packages/npm/-/blob/main/PKGBUILD?ref_type=heads

respectfully, I will close this issue

[blacklight]

@iambumblehead I've been experiencing the same issue on all of my Arch installations as well after upgrading to npm 10.

Downgrading to 9.8.1 is a temporary workaround.

Have you already reported the issue to the Arch maintainer? I couldn't find anything here https://bugs.archlinux.org/?project=1&string=npm.

I can open a ticket on the Arch side as well if you prefer.

[iambumblehead]

@blacklight please open a ticket :) I do not have an account there and did not open a ticket

[blacklight]

@iambumblehead ok FYI I've filed a bug report on Arch here https://bugs.archlinux.org/task/79693

[iambumblehead]

thanks. toolybird's comment un-necessarily rude

[blacklight]

@iambumblehead I've found the culprit and a solution - see comment on the Arch Linux thread.

Long story short, the error most likely happens when you have (or had at some point) an old version of semver installed - either an old semver package or something installed via npm install -g.

Uninstalling npm+semver, removing /usr/lib/node_modules/npm/node_modules/semver and reinstalling it should fix it.

[iambumblehead]

@blacklight yes that works thank you!

$ sudo pacman -R npm semver node-gyp
$ sudo rm -rf /usr/lib/node_modules/npm/node_modules/semver
$ sudo pacman -S npm semver
$ npm --version
10.1.0