r/reactjs • • Sep 07 '17

React 16 RC-2 available for testing

https://github.com/facebook/react/issues/10294
33 Upvotes

6 comments sorted by

4

u/[deleted] Sep 07 '17

Release 16.0.0-rc.1 on 2017-09-06

Fix error; "undefined is not a function (evaluating 'owner.getName()')" (@fxfactorial in #10448 and @bvaughn in #10520)
Improve error message when ReactDOM loads without React (@aweary in #10449)
Warn when nesting 15 subtree inside 16 (@sophiebits in #10434)
Don't warn about casing in SSR for non-HTML NS (@sophiebits in #10452)
Throw error to warn of mistaken loading of prod + dev React bundles (@flarnie in #10446)
Reset instance vars before calling commit phase lifecycles (@acdlite in #10481)
In RN skip the overhead of bridge call when it's not needed (@bvaughn in #10505)
Warn if event listener is not a function (@aweary in #10453)
Fix bug where 1k+ react roots would cause error (@acdlite in #10574)
In RN fix places where we were forcing a prepack de-optimization (@bvaughn in #10569 and #10567)
In RN fix bug related to native events that JavaScript does not know how to handle (@bvaughn in #10627)
Allow passing some "unknown" attributes through to DOM components (@nhunzaker in #10385 , #10564 , #10495 and others)
Fix bug where <select> elements defaulted to first option, even when it was 'disabled'. (@aweary in #10456 and @nhunzaker in #10142)

Release 16.0.0-rc.2 on 2017-09-06

Fix bug where React npm packages would throw an exception on startup in browsers not supporting const natively (@sophiebits in #10631)

-4

u/IMHERETOCODE Sep 08 '17

I may be confused, but wasn't React changed into something entirely different? Why are new React versions coming if it's changing to something else?

7

u/vidarc Sep 08 '17

It wasn't really changed into something entirely different. The algorithm behind deciding on what and when to render was rewritten, but most of the stuff on the top was left unchanged. React 16 is still React. There isn't a major rewrite like what happened with AngularJS -> Angular

1

u/IMHERETOCODE Sep 09 '17

Thanks for the explanation instead of the anonymous down votes I'm getting for asking a question. I hadn't paid too heavy of attention since the 0.14->15.x versioning system change. Last I had heard was there was like one unittest remaining before releasing "Fiber," which I thought was a replacement.

1

u/[deleted] Sep 09 '17

Last I had heard was there was like one unittest remaining before releasing "Fiber," which I thought was a replacement.

If you go to http://isfiberreadyyet.com/ you can track the progress of unit tests checks - it's already at 100%.

Fiber is just name of internal mechanism, the public-facing API does not change significally between 15.5 and 16.0-RC1 so all your old code should still work, and there's little "new" to learn if you've been following the best practices.

1

u/vidarc Sep 09 '17

This site can be weird. Fiber is just the name of the changes. Lin Clark has a really good overview of it on YouTube if you want to know more