Unhandled rejection (ERESOLVE)

[anthony-unicare]

• I have searched for similar issues

---

Steps to Reproduce

.ncurc:

(none)

Dependencies:

        "dependencies": {
                "@azure/identity": "^4.12.0",
                "@google-web-components/google-chart": "^5.1.0",
                "@hitc/netsuite-types": "^2025.2.1",
                "@lit/context": "^1.1.6",
                "@microsoft/microsoft-graph-client": "^3.0.7",
                "@popperjs/core": "^2.11.8",
                "@vaadin/date-picker": "^24.9.0",
                "bootstrap": "^5.3.8",
                "bootstrap-icons": "^1.13.1",
                "d3": "^7.9.0",
                "dayjs": "^1.11.18",
                "file-type-mime": "^0.4.7",
                "image-dimensions": "^2.5.0",
                "js-base64": "^3.7.8",
                "lit": "^3.3.1",
                "pdfjs-dist": "^5.4.149",
                "plotly.js-dist": "2.35.3",
                "temporal-polyfill": "^0.3.0",
                "text-encoding": "^0.7.0",
                "ts-exif-parser": "^0.2.2",
                "ts-md5": "^2.0.1",
                "xlsx": "https://cdn.sheetjs.com/xlsx-0.20.2/xlsx-0.20.2.tgz",
                "zod": "^4.1.8"
        },
        "devDependencies": {
                "@babel/cli": "^7.28.3",
                "@babel/core": "^7.28.4",
                "@babel/plugin-proposal-decorators": "^7.28.0",
                "@babel/plugin-transform-logical-assignment-operators": "^7.27.1",
                "@babel/plugin-transform-optional-chaining": "^7.27.1",
                "@babel/preset-env": "^7.28.3",
                "@babel/preset-typescript": "^7.27.1",
                "@babel/register": "^7.28.3",
                "@cspell/eslint-plugin": "^9.2.1",
                "@eslint/js": "^9.35.0",
                "@eslint/json": "^0.13.2",
                "@eslint/markdown": "^7.2.0",
                "@jest/globals": "^30.1.2",
                "@microsoft/microsoft-graph-types": "^2.40.0",
                "@oracle/suitecloud-cli": "^3.0.2",
                "@oracle/suitecloud-unit-testing": "^1.7.0",
                "@stylistic/eslint-plugin": "^5.3.1",
                "@tsconfig/strictest": "^2.0.5",
                "@types/bun": "^1.2.22",
                "@types/d3": "^7.4.3",
                "@types/extjs": "^4.2.37",
                "@types/node": "^24.5.0",
                "@types/plotly.js": "2.35.4",
                "@typescript-eslint/eslint-plugin": "^8.44.0",
                "@typescript-eslint/parser": "^8.44.0",
                "babel-loader": "^10.0.0",
                "babel-plugin-transform-amd-to-commonjs": "^1.6.0",
                "chokidar": "^4.0.3",
                "concurrently": "^9.2.1",
                "copy-webpack-plugin": "^13.0.1",
                "cross-env": "^10.0.0",
                "cspell": "^9.2.1",
                "dotenv": "^17.2.2",
                "eslint": "^9.35.0",
                "eslint-import-resolver-typescript": "^4.4.4",
                "eslint-plugin-array-func": "^5.0.2",
                "eslint-plugin-es-x": "^9.1.0",
                "eslint-plugin-eslint-comments": "^3.2.0",
                "eslint-plugin-import-x": "^4.16.1",
                "eslint-plugin-jsdoc": "^57.2.1",
                "eslint-plugin-lit": "^2.1.1",
                "eslint-plugin-lit-a11y": "^5.1.1",
                "eslint-plugin-n": "^17.23.0",
                "eslint-plugin-no-secrets": "^2.2.1",
                "eslint-plugin-notice": "^1.0.0",
                "eslint-plugin-perfectionist": "^4.15.0",
                "eslint-plugin-promise": "^7.2.1",
                "eslint-plugin-security": "^3.0.1",
                "eslint-plugin-sonarjs": "^3.0.5",
                "eslint-plugin-tsdoc": "^0.4.0",
                "eslint-plugin-unicorn": "^61.0.2",
                "eslint-plugin-wc": "^3.0.1",
                "global": "^4.4.0",
                "globals": "^16.4.0",
                "jest": "^30.1.3",
                "jshint": "^2.13.6",
                "lit-analyzer": "^2.0.3",
                "npm-check-updates": "^18.1.1",
                "npm-package-json-lint": "^9.0.0",
                "npm-run-all2": "^8.0.4",
                "open-cli": "^8.0.0",
                "patch-package": "^8.0.0",
                "rimraf": "^6.0.1",
                "terser-webpack-plugin": "^5.3.14",
                "ts-essentials": "^10.1.1",
                "ts-jest": "29.4.2",
                "ts-lit-plugin": "^2.0.2",
                "ts-node": "^10.9.2",
                "typedoc": "^0.28.13",
                "typedoc-plugin-coverage": "^4.0.1",
                "typedoc-plugin-mdn-links": "^5.0.9",
                "typedoc-plugin-zod": "^1.4.2",
                "typescript": "^5.9.2",
                "typescript-eslint": "^8.44.0",
                "webpack": "^5.101.3",
                "webpack-cli": "^6.0.1",
                "webpack-merge": "^6.0.1"
        },

Steps:

Running npm-check-updates --format group --interactive correctly identifies upgrades, but when I answer yes to run npm install to install new versions, npm exits with an error code (ERESOLVE).

Current Behavior

❯ npm run update

> @SCOPE/PACKAGE@0.0.0 update
> npm-run-all update:npm-check-updates postinstall


> @SCOPE/PACKAGE@0.0.0 update:npm-check-updates
> npm-check-updates --format group --interactive

Upgrading /mnt/c/Users/USERNAME/Projects/PACKAGE/package.json
[====================] 100/100 100%

✔ Choose which packages to update ›

 @types/node                        ^24.4.0  →   ^24.5.0
 @typescript-eslint/eslint-plugin   ^8.43.0  →   ^8.44.0
 @typescript-eslint/parser          ^8.43.0  →   ^8.44.0
 @vaadin/date-picker                ^24.8.7  →   ^24.9.0
 eslint-plugin-jsdoc                ^57.0.8  →   ^57.2.1
 eslint-plugin-n                   ^17.22.0  →  ^17.23.0
 ts-jest                             29.4.1  →    29.4.2
 typescript-eslint                  ^8.43.0  →   ^8.44.0

✔ Run npm install to install new versions? … yes
Installing dependencies...
npm error code ERESOLVE

npm error ERESOLVE could not resolve
npm error
npm error While resolving: @SCOPE/PACKAGE@0.0.0
npm error Found: @typescript-eslint/eslint-plugin@8.43.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"^8.44.0" from the root project
npm error   @typescript-eslint/eslint-plugin@"8.43.0" from typescript-eslint@8.43.0
npm error   node_modules/typescript-eslint
npm error     dev typescript-eslint@"^8.44.0" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @typescript-eslint/eslint-plugin@"^8.44.0" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/parser@8.44.0
npm error node_modules/@typescript-eslint/parser
npm error   peer @typescript-eslint/parser@"^8.44.0" from @typescript-eslint/eslint-plugin@8.44.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"^8.44.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/USERNAME/.npm/_logs/2025-09-16T02_52_04_332Z-eresolve-report.txt

npm error A complete log of this run can be found in: /home/USERNAME/.npm/_logs/2025-09-16T02_52_04_332Z-debug-0.log

Error: npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @SCOPE/PACKAGE@0.0.0
npm error Found: @typescript-eslint/eslint-plugin@8.43.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"^8.44.0" from the root project
npm error   @typescript-eslint/eslint-plugin@"8.43.0" from typescript-eslint@8.43.0
npm error   node_modules/typescript-eslint
npm error     dev typescript-eslint@"^8.44.0" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @typescript-eslint/eslint-plugin@"^8.44.0" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/parser@8.44.0
npm error node_modules/@typescript-eslint/parser
npm error   peer @typescript-eslint/parser@"^8.44.0" from @typescript-eslint/eslint-plugin@8.44.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"^8.44.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/USERNAME/.npm/_logs/2025-09-16T02_52_04_332Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/USERNAME/.npm/_logs/2025-09-16T02_52_04_332Z-debug-0.log

    at X$ (/mnt/c/Users/USERNAME/Projects/PACKAGE/node_modules/npm-check-updates/build/index.js:592:2172)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Q$ (/mnt/c/Users/USERNAME/Projects/PACKAGE/node_modules/npm-check-updates/build/index.js:594:78)
Unhandled Rejection! This is a bug and should be reported: https://github.com/raineorshine/npm-check-updates/issues
ERROR: "update:npm-check-updates" exited with 1.
❯

Expected Behavior

I’m not sure. Presumably the “unhandled rejection” should be handled.

[raineorshine]

Hi, thanks for reporting.

What version of node are you using? I was able to run npm-check-updates --format group --interactive and install the upgrades without any error using node v22.17.0.

[anthony-unicare]

node v24.8.0
npm 11.6.0

[raineorshine]

I upgraded with node v24.8.0 and npm 11.6.0 and unfortunately was still unable to reproduce. Upgrade and install went fine with no errors.

If you upgrade the dependencies and then select No to install, and then run npm install manually afterwards do you get the same result?

npm-check-updates doesn't check for peer dependency compatibility by default since it's an expensive process. You could try --peer and see if that helps. If it works, perhaps, we can detect ERESOLVE and provide a friendlier error message.