nes-react icon indicating copy to clipboard operation
nes-react copied to clipboard

Error: Could not resolve dependency: peer react@"^15.0.0 || ^16.0.0" from [email protected] node_modules/nes-react nes-react@"*" from the root project

Open lritter79 opened this issue 3 years ago • 2 comments

From the automatically generated error report: `

npm resolution error report

2021-10-18T02:09:39.181Z

While resolving: [email protected] Found: [email protected] node_modules/react react@"17.0.2" from the root project

Could not resolve dependency: peer react@"^15.0.0 || ^16.0.0" from [email protected] node_modules/nes-react nes-react@"*" from the root project

Fix the upstream dependency conflict, or retry this command with --force, or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.

Raw JSON explanation object:

{ "code": "ERESOLVE", "current": { "name": "react", "version": "17.0.2", "whileInstalling": { "name": "my-portfolio", "version": "0.1.0", "path": "C:\Users\lritter\Source\Repos\my-portfolio" }, "location": "node_modules/react", "isWorkspace": false, "dependents": [ { "type": "prod", "name": "react", "spec": "17.0.2", "from": { "location": "C:\Users\lritter\Source\Repos\my-portfolio" } } ] }, "currentEdge": { "type": "prod", "name": "react", "spec": "17.0.2", "from": { "location": "C:\Users\lritter\Source\Repos\my-portfolio" } }, "edge": { "type": "peer", "name": "react", "spec": "^15.0.0 || ^16.0.0", "error": "INVALID", "from": { "name": "nes-react", "version": "1.0.2", "whileInstalling": { "name": "my-portfolio", "version": "0.1.0", "path": "C:\Users\lritter\Source\Repos\my-portfolio" }, "location": "node_modules/nes-react", "isWorkspace": false, "dependents": [ { "type": "prod", "name": "nes-react", "spec": "*", "from": { "location": "C:\Users\lritter\Source\Repos\my-portfolio" } } ] } }, "strictPeerDeps": false, "force": false }

`

lritter79 avatar Oct 18 '21 02:10 lritter79

I have the same problem. It seems this hasn't been maintained for newer versions of React.

BenMcLean avatar Apr 16 '22 21:04 BenMcLean

@bschulte @hissalht Do you have any plans to update this library to support React 18?

Alternatively, if I create a pull request to make the library compatible with React 18, would you be willing to review and merge it?

kondo0602 avatar Mar 21 '23 15:03 kondo0602