-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Deprecated findDOMNode warning in StrictMode - originating from react-transition-group #4577
Comments
I'll update the dependency, but this won't fix the bug, which requires a new release by react-transition-group. At least, it will remove a duplicate package between us and material-ui. |
Hi, this is still happening and "react-transition-group" is at "^4.4.1" for package 'ra-ui-materialui' |
I can confirm this is still an issue and should be reopened. According to a comment on the issue over at react-transition-group this needs a client side code change.
|
I'm still having this issue with Console stack trace:
|
Any timeline on this issue? We are using react-admin for an admin panel for our client and want to ensure that this would go away at some point. Is there any workaround at the moment? |
UP |
I can't reproduce the issue on master. Could you please paste a link to a fork of the simple example CodeSandbox reproducing the issue? |
@fzaninotto I tried forking the sandbox, changing tsconfig.json, upgrading and downgrading react-admin and was also unsuccessful in reproducing the issue. However, I'm still able to reproduce the issue in a fresh project locally. Here are my exact steps:
import * as React from "react";
import { Admin, Resource, ListGuesser } from 'react-admin';
import jsonServerProvider from 'ra-data-json-server';
const dataProvider = jsonServerProvider('https://jsonplaceholder.typicode.com');
const App = () => (
<Admin dataProvider={dataProvider}>
<Resource name="users" list={ListGuesser} />
</Admin>
);
export default App;
|
I'm also getting same error. |
Still happening, |
The same. |
+1 |
2 similar comments
+1 |
+1 |
@fzaninotto I still can't pinpoint the exact reason(s) why it happens in our projects but not yours. Instructions: refresh the embedded browser page and hover over the hamburger icon to see the error in devtools |
@nmay231 Thanks for the repro. Here is the yarn.lock of your package:
It shows that the problem isn't in react-transition-group, as it is upgraded to a version that doesn't have the issue. Reproducing the bug just requires to enable And this is a known material-ui bug (mui/material-ui#13394). I'm not sure that we can do anything about it in react-admin. |
What you were expecting:
Code from the tutorial at https://marmelab.com/react-admin/Tutorial.html to run cleanly.
What happened instead:
Deprecation warning is printed to the console:
Steps to reproduce:
Other information:
The warning comes from the
react-transition-group
version imported byra-ui-materialui
(^2.2.1
, currently resolving to2.9.0
). Until recently,react-transition-group
usedfindDOMNode
, which is deprecated from React 16.6.0.The bug in
react-transition-group
was fixed recently (reactjs/react-transition-group#429) but not yet released. It would be nice ifra-ui-materialui
could depend onreact-transition-group@4
so when the fix is released, it will be picked up automatically.@material-ui/core
already depends onreact-transition-group@4.3.0
internally so I believe there would not be any issue.Environment
The text was updated successfully, but these errors were encountered: