Upgrade to React 0.14 and React Router 1.0 about gatsby HOT 15 CLOSED

Upgrade guide here.

from gatsby.

am interested in working on this one. @KyleAMathews, looks like, for react-router, the files to edit are static-entry and web-entry. Is that right?

Also, do you want to wait until actual releases? or have an implementation that uses the rc1 of each?

from gatsby.

That'd be great! Yeah those two +
https://github.com/gatsbyjs/gatsby/blob/master/lib/isomorphic/create-routes.coffee
which
is where React Routes are actually created. Everything else should stay
the same. Feel free to convert things to ES6 if you'd like as you go.

Thanks! Looking forward to your PR.

Oh and on timing, let's wait to do an actual release when both of their
1.0s are released. Perhaps do our own rc release if they're taking their
times.

On Thu, Sep 17, 2015 at 10:23 AM Phlogistic Fugu [email protected]
wrote:

am interested in working on this one. @KyleAMathews
https://github.com/KyleAMathews, looks like, for react-router, the
files to edit are static-entry and web-entry. Is that right?

Also, do you want to wait until actual releases? or have an implementation
that uses the rc1 of each?

—
Reply to this email directly or view it on GitHub
#32 (comment).

from gatsby.

API shouldn't change while they move out from -rc, should they?

from gatsby.

Re: ES6 conversion
Thanks, yeah I prefer JS/ES6 to coffeescript actually, but didn't want to rock the boat unnecessarily.

Re: releases and rc1
Yep it wouldn't quite be right to have a "production" release that has "non-production" dependencies. How about a new branch: react-router-v1.0 for work on this until the official release?

from gatsby.

The API shouldn't change no. I'm more concerned about potential bugs. But also as far as Gatsby is concerned, users of gatsby are pretty insulated from both router and react so upgrading is more of a keeping up with times than any major improvements.

Well other than code splitting on routes. That'll be very nice as people start to build bigger sites on gatsby.

from gatsby.

There's an issue already btw for code splitting #10

Also @phlogisticfugu converting to ES6 is the plan so not at all boat rocking :) @gesposito has actually been converting the starter sites + wrapper components recently.

from gatsby.

Hey @KyleAMathews I can work on react router upgrade. Should I just send a PR?

from gatsby.

Thanks @knowbody!

from gatsby.

Yep sorry I didn't end up submitting a PR, things have gotten hectic so I haven't gotten to playing with this. glad to see you jumping in @knowbody !

from gatsby.

#111
I'm in the process of finalizing the complete upgrade which included ES6 as well as newest React-router & Babel 6 + other improvements

from gatsby.

@knowbody how close is RR 2.0 to landing?

from gatsby.

https://twitter.com/ryanflorence/status/681737658532364290

from gatsby.

https://github.com/rackt/react-router/blob/master/upgrade-guides/v2.0.0.md

from gatsby.

0.8 has React-Router 2.0 now 🎉

from gatsby.