Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended
See original GitHub issueEasily recreatable when accessed in <React.StrictMode>
. Any suggestions or recommendations for this one would be highly appreciated.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Using UNSAFE_componentWillReceiveProps in strict mode is ...
Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code.
Read more >javascript - React warning for Using ... - Stack Overflow
I am very beginner in react and i got stacked with a warning, I can not resolve them even i read a lot...
Read more >warning: using unsafe_componentwillmount in strict mode is ...
Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. * Move data fetching code or side effects...
Read more >Using strict mode in React 18: A guide to its new behaviors
Introduction to React's strict mode · Warnings on the use of unsafe lifecycle methods · Recommending the createRef API over the legacy string...
Read more >Using UNSAFE_componentWillReceiveProps in strict ... - velog
Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. · Warning · Solution.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Hassan-Zahid FYI, this is already released as an alpha version, you can install it with:
yarn add react-google-places-autocomplete@3.0.0-alpha.1
And you can find the new docs here
@Hassan-Zahid I’m not sure if there’s something for you to do on your side, the library needs an update to stop using that and move to
componentDidUpdate
.I’m not sure when I’ll be able to take a look a this, but PRs are welcomed!