Due to the recent frequent supply chain attacks, I set min-release-age for npm in ~/.npmrc.
However, this causes Mason to fail when updating language servers, which leads to an error message every time I open Neovim. Below is the message in Mason.
◍ oxlint
▶ # [29/29] npm error A complete log of this run can be found in: /home/fesmoph/.npm/_logs/2026-05-29T11_04_56_840Z-debug-0.log
The log message is as follows.
0 verbose cli /usr/bin/node /home/fesmoph/.bun/bin/npm
1 info using npm@11.14.1
2 info using node@v22.22.1
3 silly config load:file:/home/fesmoph/.bun/install/global/node_modules/npm/npmrc
4 silly config load:file:/home/fesmoph/.local/share/nvim/mason/staging/oxlint/.npmrc
5 silly config load:file:/home/fesmoph/.npmrc
6 silly config load:file:/usr/etc/npmrc
7 verbose title npm install oxlint@1.67.0
8 verbose argv "install" "oxlint@1.67.0"
9 verbose logfile logs-max:10 dir:/home/fesmoph/.npm/_logs/2026-05-29T10_49_45_946Z-
10 verbose logfile /home/fesmoph/.npm/_logs/2026-05-29T10_49_45_946Z-debug-0.log
11 silly logfile start cleaning logs, removing 4 files
12 silly packumentCache heap:2197815296 maxSize:549453824 maxEntrySize:274726912
13 silly logfile done cleaning log files
14 silly idealTree buildDeps
15 silly fetch manifest oxlint@1.67.0
16 silly packumentCache full:https://registry.npmjs.org/oxlint cache-miss
17 http fetch GET 200 https://registry.npmjs.org/oxlint 785ms (cache updated)
18 silly packumentCache full:https://registry.npmjs.org/oxlint set size:undefined disposed:false
19 silly placeDep ROOT oxlint@ OK for: @mason/oxlint@1.0.0 want: 1.67.0
20 verbose type version
21 verbose stack oxlint: No matching version found for oxlint@1.67.0 with a date before 5/22/2026, 6:49:45 PM.
21 verbose stack at module.exports (/home/fesmoph/.bun/install/global/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:210:23)
21 verbose stack at RegistryFetcher.manifest (/home/fesmoph/.bun/install/global/node_modules/npm/node_modules/pacote/lib/registry.js:130:54)
21 verbose stack at async #fetchManifest (/home/fesmoph/.bun/install/global/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1249:20)
21 verbose stack at async #nodeFromEdge (/home/fesmoph/.bun/install/global/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1086:19)
21 verbose stack at async #buildDepStep (/home/fesmoph/.bun/install/global/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:930:15)
21 verbose stack at async Arborist.buildIdealTree (/home/fesmoph/.bun/install/global/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:169:7)
21 verbose stack at async Promise.all (index 1)
21 verbose stack at async Arborist.reify (/home/fesmoph/.bun/install/global/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:111:5)
21 verbose stack at async Install.exec (/home/fesmoph/.bun/install/global/node_modules/npm/lib/commands/install.js:149:5)
21 verbose stack at async Npm.exec (/home/fesmoph/.bun/install/global/node_modules/npm/lib/npm.js:193:9)
22 error code ETARGET
23 error notarget No matching version found for oxlint@1.67.0 with a date before 5/22/2026, 6:49:45 PM.
24 error notarget In most cases you or one of your dependencies are requesting a package version that doesn't exist.
25 silly unfinished npm timer reify 1780051786147
26 silly unfinished npm timer reify:loadTrees 1780051786149
27 verbose cwd /home/fesmoph/.local/share/nvim/mason/staging/oxlint
28 verbose os Linux 6.6.114.1-microsoft-standard-WSL2
29 verbose node v22.22.1
30 verbose npm v11.14.1
31 verbose exit 1
32 verbose code 1
33 error A complete log of this run can be found in: /home/fesmoph/.npm/_logs/2026-05-29T10_49_45_946Z-debug-0.log
Is there any way to resolve this issue, or to only update packages that meet the requirement? Thanks!
Due to the recent frequent supply chain attacks, I set min-release-age for npm in
~/.npmrc.However, this causes Mason to fail when updating language servers, which leads to an error message every time I open Neovim. Below is the message in Mason.
The log message is as follows.
Is there any way to resolve this issue, or to only update packages that meet the requirement? Thanks!