-
Notifications
You must be signed in to change notification settings - Fork 27.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
Start testing Fiber #1098
Comments
Here's an example on how to opt into low priority updates: |
React 16 Beta is out now for public testing. |
Yes, nothing in |
@gaearon Thanks. Basically we want to track errors happening inside the component. Is that the way we should do it? |
Seems reasonable to me. |
Yeah! I got that. (Actually, that's good in a sense) |
This also happens when trying to switch to Preact (and using the example provided).
|
So React 16 is out now, any updates about it? Because I still have an error:
|
Yeah me too @dmt-13 |
@dmt-13 and @bntzio : as per latest README (not sure when it was updated), you'll either need to use |
Yep, I just got it working, you need:
|
FYI, I just tried to update our app from Next.js 2.0 / React 15 to Next.js 4.0 / React 16, and except for a few warnings related to SSR / Client rehydration (on very edge cases, not critical at all), everything worked perfectly! So, thank you to all contributors, this is amazing! |
@damusnet great to hear ❤️ Closing this ticket 👍 |
@timneutkens Have you tried in IE11? |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
react@16.0.0-alpha.2
react-dom@16.0.0-alpha.2
We'll need to use the following:
require('react-dom/fiber')
The text was updated successfully, but these errors were encountered: