Skip to content

Conversation

remarcable
Copy link

Installing react-lazily-render in a project using React 17 or 18 fails with the following error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"18.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.1.1" from [email protected]
npm ERR! node_modules/react-lazily-render
npm ERR!   react-lazily-render@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

A workaround is using npm install react-lazily-render --force which works without problems. As the package is working in newer React versions already, I propose updating its peer dependencies. Generally, though, we should re-run the tests against the newer versions of React to see if anything breaks.

Installing `react-lazily-render` in a project using React 17 or 18 fails with the following error:

```
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"18.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.1.1" from [email protected]
npm ERR! node_modules/react-lazily-render
npm ERR!   react-lazily-render@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
```

A workaround is using `npm install react-lazily-render --force` which works without problems. As the package is working in newer React versions already, I propose updating its peer dependencies. Generally, though, we should re-run the tests against the newer versions of React to see if anything breaks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant