[email protected]
[email protected]
We'll need to use the following:
require('react-dom/fiber')
Here's an example on how to opt into low priority updates:
https://github.com/facebook/react/blob/master/examples/fiber/index.html#L136
React 16 Beta is out now for public testing.
I just tried Next.js with React 16 Beta and it throw this error.
It looks like Next.js is using a internal lib and React 16 doesn't expose them anymore.
Yes, nothing in /lib/
will be exposed in 16. Happy to discuss specific use cases for internals in https://github.com/facebook/react/issues/10294.
@gaearon Thanks.
We've a PR for this: https://github.com/zeit/next.js/pull/2570/files
Basically we want to track errors happening inside the component.
In the ^^ above PR, is uses some method in Fiber.
Is that the way we should do it?
@gaearon I started it here: https://github.com/zeit/next.js/pull/2659
Let me know I'm doing it good here.
Seems reasonable to me.
Note that this isn鈥檛 supported on server side yet (but normal catch
works there).
Yeah! I got that. (Actually, that's good in a sense)
We've already catch errors on the server. So, I hope we are good to go.
This also happens when trying to switch to Preact (and using the example provided).
ERROR Failed to compile with 1 errors 7:40:58 PM
This module was not found:
* react-dom/lib/ReactReconciler in ./~/next/dist/client/next-dev.js
To install it, you can run: npm install --save react-dom/lib/ReactReconciler
> Ready on http://localhost:3000
So React 16 is out now, any updates about it? Because I still have an error:
* react-dom/lib/ReactReconciler in ../node_modules/next/dist/client/next-dev.js
To install it, you can run: npm install --save react-dom/lib/ReactReconciler
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 next@beta
to use react 16+, or if you want to use stable next, install react and react-dom @15
(npm i next react@15 react-dom@15
or npm i next@beta react react-dom
)
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.
Most helpful comment
Yep, I just got it working, you need: