Skip to content
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 18: Console Errors when using Flip Move "Using UNSAFE_componentWillReceiveProps" "findDOMNode is deprecated in StrictMode" #270

Open
douglasg14b opened this issue Apr 25, 2022 · 3 comments

Comments

@douglasg14b
Copy link

This seems like things have been deprecated that flipmove is using?

I'm using React 18

image

react_devtools_backend.js:3973 Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.

  • Move data fetching code or side effects to componentDidUpdate.
  • If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://reactjs.org/link/derived-state

Please update the following components: FlipMove

And

Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of FlipMove which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here:

@douglasg14b douglasg14b changed the title React 18: Console Errors wHen using Flip Move "Using UNSAFE_componentWillReceiveProps" "findDOMNode is deprecated in StrictMode" React 18: Console Errors when using Flip Move "Using UNSAFE_componentWillReceiveProps" "findDOMNode is deprecated in StrictMode" Apr 25, 2022
@peterwiebe
Copy link

Have you tried fixing the issue? @douglasg14b

@douglasg14b
Copy link
Author

Can you expand on that?

@peterwiebe
Copy link

@douglasg14b you can ignore my question. I have switched to https://github.com/aholachek/react-flip-toolkit instead since this library is no longer maintained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants