-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Error related to RefFindNode and React 17 #4124
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you've completed all the fields in the issue template so we can best help. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
@silviubogan can you please provide an isolated example? |
Closing this for housekeeping until we will have an isolated repro 😿 P.S. For sure we are open to accept fixes if you will be able to debug the issue. |
If However, it's really strange that issue came from React's upgrade. |
A simple Button gives the same error in React 17 and up. Downgrading to react 16.x.x removes the error. There's a lot of npm packages which suffer the same issue! |
@danydhondt feel free to make a repro case then |
Bug Report
Steps
Clone my fork of the project on which I work: https://github.com/silviubogan/volto-slate/tree/eefee2c46c38bc7bd07e6a9681e27bebc6fc5983 into a new directory and
cd
into it.Run this (fish syntax for putting output of
pwd
in the command):Expected Result
The unit tests are passed.
Actual Result
There are some strange errors related to RefFindNode and I think they are related to React 17. I put here just the first jest test file that fails as the others present similar errors:
Version
2.0.1
Testcase
I think the steps to reproduce are easier to follow than a possible testcase.
The text was updated successfully, but these errors were encountered: