You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you reporting a bug, or opening a feature request?
Bug associated with installation - it appears to be a conflict in package requirements
What is the actual behavior/output?
Unable to install the react-d3-tree package when react-native is on version 0.74
What is the behavior/output you expect?
Installation succeeds without any issue
Can you consistently reproduce the issue/create a reproduction case (e.g. on https://codesandbox.io)?
Yes, tried several times, same outcome.
What version of react-d3-tree are you using?
3.6.2
If react-d3-tree crashed with a traceback, please paste the full traceback below.
Here is the npm installation failure message:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR! peer react@"" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/core
npm ERR! @react-navigation/core@"^6.4.15" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/native
npm ERR! peer @react-navigation/native@"^6.0.0" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/elements
npm ERR! @react-navigation/elements@"^1.3.29" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/native-stack
npm ERR! 1 more (@react-navigation/stack)
npm ERR! 3 more (@react-navigation/native-stack, ...)
npm ERR! peer react@"" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/elements
npm ERR! @react-navigation/elements@"^1.3.29" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/native-stack
npm ERR! @react-navigation/native-stack@"^6.9.25" from the root project
npm ERR! @react-navigation/elements@"^1.3.29" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/stack
npm ERR! @react-navigation/stack@"^6.3.21" from the root project
npm ERR! 21 more (@react-navigation/native, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! react-d3-tree@"" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR! peer react@"^18.3.1" from [email protected]
npm ERR! node_modules/react-dom
npm ERR! peer react-dom@"16.x || 17.x || 18.x" from [email protected]
npm ERR! node_modules/react-d3-tree
npm ERR! react-d3-tree@"" 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.
Do note that react-native v0.74 requires react to be on version 18.2.0, however react-d3-tree needs it on 18.3.1. Upgrading react to 18.3.1 did not help as it breaks react-native 0.74 dependencies.
I am new to react-native development so this could be a rookie mistake that I am doing. Appreciate any help on this. Thanks!
The text was updated successfully, but these errors were encountered:
Are you reporting a bug, or opening a feature request?
Bug associated with installation - it appears to be a conflict in package requirements
What is the actual behavior/output?
Unable to install the react-d3-tree package when react-native is on version 0.74
What is the behavior/output you expect?
Installation succeeds without any issue
Can you consistently reproduce the issue/create a reproduction case (e.g. on https://codesandbox.io)?
Yes, tried several times, same outcome.
What version of react-d3-tree are you using?
3.6.2
If react-d3-tree crashed with a traceback, please paste the full traceback below.
Here is the npm installation failure message:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR! peer react@"" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/core
npm ERR! @react-navigation/core@"^6.4.15" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/native
npm ERR! peer @react-navigation/native@"^6.0.0" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/elements
npm ERR! @react-navigation/elements@"^1.3.29" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/native-stack
npm ERR! 1 more (@react-navigation/stack)
npm ERR! 3 more (@react-navigation/native-stack, ...)
npm ERR! peer react@"" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/elements
npm ERR! @react-navigation/elements@"^1.3.29" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/native-stack
npm ERR! @react-navigation/native-stack@"^6.9.25" from the root project
npm ERR! @react-navigation/elements@"^1.3.29" from @react-navigation/[email protected]
npm ERR! node_modules/@react-navigation/stack
npm ERR! @react-navigation/stack@"^6.3.21" from the root project
npm ERR! 21 more (@react-navigation/native, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! react-d3-tree@"" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR! peer react@"^18.3.1" from [email protected]
npm ERR! node_modules/react-dom
npm ERR! peer react-dom@"16.x || 17.x || 18.x" from [email protected]
npm ERR! node_modules/react-d3-tree
npm ERR! react-d3-tree@"" 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.
Do note that react-native v0.74 requires react to be on version 18.2.0, however react-d3-tree needs it on 18.3.1. Upgrading react to 18.3.1 did not help as it breaks react-native 0.74 dependencies.
I am new to react-native development so this could be a rookie mistake that I am doing. Appreciate any help on this. Thanks!
The text was updated successfully, but these errors were encountered: