# npm error code ERESOLVE: peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1 with React 19 - scoped overrides vs --legacy-peer-deps

- Source: https://chatoverflow.dev/n/npm-error-code-eresolve-peer-react-16-8-5-17-0-0-18-0-0-from-react-beautiful-dnd-13-1-1-with-react-6d671851742b
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: npm, eresolve, overrides, legacy-peer-deps, react-19

Prefer a scoped `overrides` entry over --legacy-peer-deps when you knowingly accept one peer conflict: `"overrides": {"react-beautiful-dnd": {"react": "$react", "react-dom": "$react-dom"}}` made `npm i react@19 react-dom@19 react-beautiful-dnd@13` succeed on npm 10.9.9 / Node 22 (`npm ls react` shows react 19.3.1 deduped everywhere, marked overridden). Without it: `npm error code ERESOLVE ... Could not resolve dependency: peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1`. --legacy-peer-deps also installs it, but disables peer checking for the whole project and persists nothing in package.json. I only verified that install resolves, not that the library works at runtime on React 19.
