#2072·npm-check-updates

updates available but not recognized and not applied

Author: syriuszbCreated Sep 7, 2026Updated Sep 7, 2026

[yes] I have searched for similar issues

Not found.

[yes] I am using the latest version of npm-check-updates

$ ncu -v
23.1.0

[yes] I am using a compatible version of node

$ node -v
v26.8.1

Steps to Reproduce

.ncurc:

$ cat ~/.ncurc.json 
{
  "peer": true,
  "cooldown": 3
}

npm:

$ npm -v
12.0.2

Dependencies:

$ cat package.json 
{
  ...
  "dependencies": {
    "react": "19.2.8",
    "react-dom": "19.2.8"
  },
  "devDependencies": {
    "@eslint/js": "9.39.1",
    "@vitejs/plugin-react": "6.1.0",
    "eslint": "9.39.5",
    "eslint-plugin-react": "7.37.5",
    "eslint-plugin-react-hooks": "7.1.1",
    "globals": "17.11.0",
    "vite": "8.2.2"
  }
}

Steps:

$ ncu
Using config file /home/[...redacted...]/.ncurc.json
Checking /home/[...redacted...]/vite-project/package.json
[====================] 9/9 100%
[====================] 9/9 100%
[====================] 3/3 100%
All dependencies not in cooldown match the latest package versions :)
[====================] 4/4 100%

Ignored incompatible updates (peer dependencies):

 @eslint/js             9.39.1  →   10.0.1  reason: @eslint/js requires eslint ^10.0.0
 @vitejs/plugin-react    6.1.0  →    6.1.1  reason:
 eslint                 9.39.5  →   10.9.1  reason: eslint-plugin-react requires ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7
 globals               17.11.0  →  17.12.0  reason:

Current Behavior

There are updates available for packages @vitejs/plugin-react and globals and there is no reason to skip these updates (no peer dependency problems, no cooldown period), but no such updates are applied and ncu sees these packages in incompatible section (as shown above).

Expected Behavior

Both packages @vitejs/plugin-react and globals should be updated and other incompatible packages should be skipped.

Source: raineorshine/npm-check-updates

View original on GitHub View discussion on GitHub