3 ms·
Not so much; it's more or less a drop-in replacement. Improvements to our workflow and build tooling are needed, but we were able to make the switch without cha
by huehehue 9y ago
Not so much; it's more or less a drop-in replacement. Improvements to our workflow and build tooling are needed, but we were able to make the switch without changing much.
We do have our own patches scattered throughout core React stuff, so it was tricky carrying those over. Also needed to build React from the commit before they destroyed React.PropTypes & React.createClass because many third-party libs still need those.
- whatnotests 9y agoInteresting-- that will definitely be something we deal with for some time. An article from you and your team about what to do/not to do during the migration and on the road ahead could be good PR and mutually beneficial to all parties involved. Hope you publish something when you can!