Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
When will react-fiber be officially released? #9463
I wonder if there’s any specific place these concerns are coming from? If there’s a blog post raising panic we’d like to know
Yes, React 16 is using Fiber, but in a compatibility mode. All async features are disabled for better compatibility.
This is incorrect by the way. React 16 operates in compatibility mode. There are no changes to
Fiber is not a new React API. The internals have changed, but the API stays the same. There are virtually no breaking changes in React 16 associated with Fiber itself.
We do have some breaking changes in React 16 (such as moving
You won’t be “doomed”. If Fiber works out of the box for 30,000 existing components in Facebook codebase, it will likely work for your codebase too.
There is no specific date. It is likely going to be released this summer but we don’t know exactly. But there is no point in waiting for it, just like there was no point in waiting for React 0.14, or React 15. This is just a regular version update, and it works the same way as before.
Hope this addresses your concerns!
As far as I can tell, using React since 0.5.2, the core API has always been very stable because the underlying principles remained the same over time.
Except few breaking changes mostly due to language evolutions (like createClass/mixins => ES6 class) you can probably start at React n and migrate to React n+3 without too much pain. I expect this to remain true in the future as well. Bonus: codemods are provided to help so sometimes a migration can be done in 5 minutes.
I can attest to that. I've been using React for almost two years and there has never been a breaking change. Old features are deprecated in the next release but continue to work, and then removed in next+1 release (which is usually at least 6 months later). So you can always upgrade to latest version and have a couple of months to gradually update your code (which is relatively simple thanks to codemods and warnings that tell you exactly what to change).
Compare that, for example, with Angular where major releases require you to update your entire app at once (or be stuck with the old version).
Will there be a way to enable async features for even more forward leaning codebases, or are they/their documentation incomplete for React 16?
We are still figuring it out for our own codebases. There will likely be some unstable API, you can track #9448 for the discussion.
As of now, there are known bugs in async mode.