-
Notifications
You must be signed in to change notification settings - Fork 586
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
Support React 16.9 #681
Support React 16.9 #681
Conversation
+1 👍 |
Are there any plans to merge this PR? |
Tangentially related. moroshko/react-autowhatever#51 (PR for updating the |
+1 |
When will a release be cut with this? |
|
I removed "babel-plugin-transform-react-remove-prop-types" and build gonna ok |
If the tests are not passing can we merge this please. |
@moroshko I just wanted to follow up and see if a release could be cut with these changes - thanks! |
when can we expect release with this fix? |
@moroshko We only have about 10 more months before ComponentWillReceiveProps is removed from React version 17. I hope the CDN can be updated before then. |
After #672 was posted @aberezkin has stepped up to start maintaining, and so this PR was finally merged today. Still, this project could use some additional steward(esse)s, so reach out if you want to help maintain this, ref. the call for maintainers on the README |
Thank you for this. When can we expect an updated npm package to be available? |
@obryckim, I'm planning to release a new major version in a week or two after I update all dependencies and build scripts. |
Please post here when you merge - I am dealing with this issue too and it's flooding my test output :( |
@dfenske If you just need to silence the output, fork the repo and publish a private fork to NPM edit: You don't even need to publish an NPM package. NPM can use Github directly, so just point it to |
Or use |
Whaaat, that's amaaaazing. Not at all surprised to see you here, as well, @SimenB 😄 |
componentWillReceiveProps => UNSAFE_componentWillReceiveProps
Seems fixed, but never released. Who can take care of this? |
@ademidun That is incorrect. This was merged in first half of 2020. There has been many releases published since then, last time in January 2021. https://www.npmjs.com/package/react-autosuggest?activeTab=versions
Also answered by reading this thread. |
Well, it's confusing since I use |
@adi518 react-command-palette is on react-autosuggest v10.0.1. I've been unable to reproduce your error, we can continue to troubleshoot you issue outside this repo |
GitHub collapses the last three releases (probably because they have a short description or none) so I missed it. |
I'm getting this warning in strict mode, so unfortunately, this issue and the PR that fixed it are irrelevant. This is the relevant issue: #624. I'm using React 17 in strict mode. |
This PR doesn't add support for React 16.9. This change now throws another warning:
|
Add UNSAFE_ to lifecycle methods, otherwise, React 16.9 raises a warning