npm cannot pick a compatible set of dependencies because peer requirements conflict. Align versions (or upgrade both sides) and reinstall.
npm v7+ enforces peer dependencies strictly. When two packages demand incompatible peer versions (e.g., plugin wants React 17 while you installed React 18), the resolver aborts with ERESOLVE and shows a conflict tree.
npm prints the conflicting packages. Read the requested vs installed versions to identify which pair is incompatible.
Pick compatible versions (upgrade/downgrade both). Example for React:
npm install react@17 react-dom@17
# or upgrade plugin to support React 18
npm install some-plugin@latestAfter adjusting versions, reinstall to refresh the lockfile:
rm -rf node_modules package-lock.json
npm installIf you must force a version, add an override in package.json:
{
"overrides": {
"some-plugin/react": "18.0.0"
}
}Re-run npm install. Test carefully because forced peers may break runtime.
Avoid --legacy-peer-deps as a long-term fix; it skips peer validation and can hide real incompatibilities. Prefer aligning the ecosystem on the same major version.
npm ERR! code ENOAUDIT npm ERR! Audit endpoint not supported
How to fix "npm ERR! code ENOAUDIT - Audit endpoint not supported"
npm ERR! code EBADDEVENGINES npm ERR! devEngines.runtime incompatible with current node version
How to fix "npm ERR! code EBADDEVENGINES - devEngines.runtime incompatible with current node version"
npm ERR! code ETOOMANYARGS npm ERR! Too many arguments
How to fix "npm ERR! code ETOOMANYARGS - Too many arguments"
npm ERR! code EINVALIDTAGNAME npm ERR! Invalid tag name: tag names cannot contain spaces
How to fix "npm ERR! code EINVALIDTAGNAME - tag names cannot contain spaces"
npm ERR! code E400 npm ERR! 400 Bad Request
How to fix "npm ERR! code E400 - 400 Bad Request" error