-
-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency error with react-virtual
#330
Comments
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/react
npm WARN peer react@"^16.8 || ^17.0 || ^18.0" from @radix-ui/[email protected]
npm WARN node_modules/@radix-ui/react-compose-refs
npm WARN @radix-ui/react-compose-refs@"1.0.1" from @radix-ui/[email protected]
npm WARN node_modules/@radix-ui/react-slot
npm WARN 45 more (@radix-ui/react-context, @radix-ui/react-dialog, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.6.3 || ^17.0.0" from [email protected]
npm WARN node_modules/kbar/node_modules/react-virtual
npm WARN react-virtual@"^2.8.2" from [email protected]
npm WARN node_modules/kbar
npm WARN
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/react
npm WARN peer react@"^16.6.3 || ^17.0.0" from [email protected]
npm WARN node_modules/kbar/node_modules/react-virtual
npm WARN react-virtual@"^2.8.2" from [email protected]
npm WARN node_modules/kbar Encountered the same error, I tried several attempts to override or npm-force-resolution but was not able to fix it. As far as I know, there is no breaking effect towards the usage of kbar, but it would be nice to get rid of the warning messages |
with npm 9+ you can define dep overrides for a workaround: package.json ...
"overrides": {
"react": "18.2.0"
}, https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides |
This works to get rid of the warning but sadly most my projects followed the LTS version of nodejs and npm. Thanks tho! |
Facing the same warning. Is there anything we can do to help fix this? |
react-virtual is now available as v3 and published under @tanstack/react-virtual. The old version will not receive updates anymore, see cloudscape-design/components#1765 (comment). Fixes timc1#330
I created #348 to fix this. @ahmadbilaldev If you want to help, test that PR in your project and see if you can find any issues. |
react-virtual is now available as v3 and published under @tanstack/react-virtual. The old version will not receive updates anymore, see cloudscape-design/components#1765 (comment). Fixes timc1#330
commit 51879c7 Author: Felix Uhl <[email protected]> Date: Sun Dec 10 17:15:24 2023 +0100 Fix type error commit a19a064 Author: Felix Uhl <[email protected]> Date: Sun Dec 10 15:29:40 2023 +0100 Upgrade to react-virtual 3.0.1 react-virtual is now available as v3 and published under @tanstack/react-virtual. The old version will not receive updates anymore, see cloudscape-design/components#1765 (comment). Fixes timc1#330
react-virtual is now available as v3 and published under @tanstack/react-virtual. The old version will not receive updates anymore, see cloudscape-design/components#1765 (comment). Fixes timc1#330
react-virtual is now available as v3 and published under @tanstack/react-virtual. The old version will not receive updates anymore, see cloudscape-design/components#1765 (comment). Fixes timc1#330
react-virtual is now available as v3 and published under @tanstack/react-virtual. The old version will not receive updates anymore, see cloudscape-design/components#1765 (comment). Fixes timc1#330
react-virtual is now available as v3 and published under @tanstack/react-virtual. The old version will not receive updates anymore, see cloudscape-design/components#1765 (comment). Fixes timc1#330
Hey! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bad bot. Issue persists, PR to fix it was opened already. |
Please if we can get this fixed. |
PLease maintain this and get this fixed |
need some noise here! |
Bump |
bump |
please bump |
I still get an error when I install packages based on react 18 even though #222. Do you have any ideas how to solve it?
The text was updated successfully, but these errors were encountered: