-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Enzyme Internal Error: unknown node with tag 12 #1620
Comments
@kkwiatkowski this is a duplicate of #1509, which has already been fixed by #1513. Just waiting on a release by enzyme 😢 |
@baldwmic thanks for your answer. For some reason I couldn't find anything around it. |
Did this fix get released yet? |
No, not yet. Please be patient. |
Sorry to ping here, but any ETA on the release? This is blocking a lot of people, I'd suspect. Basically we aren't able to move to the new context without breaking existing enzyme tests. |
No ETA just yet. I understand the frustration and that it's blocking many people, including Airbnb, from using many of React 16's new features. It will be released as soon as it's ready. |
@ljharb just chiming in to say thanks for taking the time to do it right. Enzyme is an amazing library! |
@ljharb Is there an issue we can follow that isn't closed to check on the progress of a fix here getting published? |
@ljharb Thank you! 😄 |
The following packages are now released: |
I got this problem with "enzyme": "^3.9.0" |
@Fl4v10 please file a new issue |
Current behavior
React in version 16.3 introduces new Context API. That API comes with two new node types (12 and 13).
These node types are not supported and therefore
enzyme-adapter-react-16
is throwing an error:# for ContextConsumer Enzyme Internal Error: unknown node with tag 12
or
# for ContextProvider Enzyme Internal Error: unknown node with tag 13
when you use Context API inside your React components.
An example:
Expected behavior
New node types are handled correctly.
API
Version
Adapter
The text was updated successfully, but these errors were encountered: