-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
React 17 support in peerDeps range #58
Comments
Yea was planning on making that change soon. Should probably work fine with React 17 since it only changes event capture and I'll have to update the devDep and make sure tests pass first. Might get to it in the coming week as I've been looking to get back to this library and make some merges I put off. In any case, it's just a warning, so it should not be a blocker. |
Would you accept a PR if everything works? I like to strictly follow peerDependency ranges so this may block our upgrade soon. |
Would also be open to lend a hand if needed |
This comment has been minimized.
This comment has been minimized.
Now that npm v7 has been released, this is becoming more of a blocker to upgrading. npm@7 throws an error if peerDeps cannot be resolved correctly. |
This comment has been minimized.
This comment has been minimized.
any quick workaround to make this work on react 17? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hi all. I have created an npm package as a workaround for the React 17 issue https://www.npmjs.com/package/react-signature-drawing. This has a direct dependency on this project. This should be used until agilgur5 is back |
Hi @luke9216 how to use your package? |
This comment was marked as spam.
This comment was marked as spam.
Released in v1.0.5 |
This module does not currently allow React 17 in it's peerDependency range. Requesting that this would be allowed.
The text was updated successfully, but these errors were encountered: