Closed productiveme closed 3 years ago
@productiveme any specific issue for closing this?
I don't think its needed to require latest react, my issue was a problem with dependency resolution between React 16, 17.0.1 and 17.0.2 and after testing with this plugin on a higher version, I still have other conflicts between plugins. Seems this is the wrong avenue to resolve the problem.
Got it!
same kind of issue here, many of our deep dependencies require react v16.x and the new tech we wanna try supports only react v17 or above.
So, thought an upgrade of all deps and their deep deps should solve it (unfortunately none has react v17 supported yet)🤞
though this won't solve the conflicts, I would still suggest to keep this open as this has to be done sooner or later.
Ideally, we would want the package to support both v16 and v17.
So the peerDependency
would be something like:
"react": "^16.0.0 || ^17.0.0"
Description
React updated to 17.0.2
Motivation and Context
It causes dependency issues with latest gatsby
How Has This Been Tested?
npm t
passes all testsScreenshots (if appropriate):
Types of changes
Checklist: