Closed troelsfr closed 2 years ago
Maybe you can try react 17. I am not sure if the component is compatible with react 18。
@xzdarcy @troelsfr Hey, I run into the same issue today.
This is the log I got from yarn on the peer-requirements
Maybe it provides any of you with more insight.
Could we just update the peer dependency of react-virtualized
to react '17' || '18'
to make this pass? Unless react-virtualized
is using something explicitly from a previous react version that is no longer available It shouldnt be an issue (at least at first glance).
P.S. This package does look very nice, I'm only now starting to look at as it seems to be doing things no other library does, and especially in an open format (not too restricting).
@xzdarcy small update,
https://github.com/bvaughn/react-virtualized/blob/master/package.json
From the react-virtualized
package.json it looks like it accepts up to version 18
"peerDependencies": {
"react": "^15.3.0 || ^16.0.0-alpha || ^17.0.0 || ^18.0.0",
"react-dom": "^15.3.0 || ^16.0.0-alpha || ^17.0.0 || ^18.0.0"
},
So maybe this is just a bump-up in this repo's package.json
?
P.S. If there is a way we could be of help I would be glad to participate.
@xzdarcy small update, https://github.com/bvaughn/react-virtualized/blob/master/package.json From the
react-virtualized
package.json it looks like it accepts up to version 18"peerDependencies": { "react": "^15.3.0 || ^16.0.0-alpha || ^17.0.0 || ^18.0.0", "react-dom": "^15.3.0 || ^16.0.0-alpha || ^17.0.0 || ^18.0.0" },
So maybe this is just a bump-up in this repo's
package.json
?P.S. If there is a way we could be of help I would be glad to participate.
Thanks, it is work. I have fixed it and released a new version 0.1.2.
First of all, this component looks amazing!
Following the instructions in the
README.md
and installing the component into my project, I get following error:Here are the packages I am using: