Hacker News new | past | comments | ask | show | jobs | submit login

React has actually done a great job of providing clear upgrade paths, assuming you don't try to jump several major versions at a time.

They generally provide deprecation warnings at least 1 major version before actually breaking/removing an existing API. They have also started providing codemod scripts to help migrate a large codebase (though I've found find/replace sufficient for a lot of them)

My bigger problem has been relying on 3rd party components that hold me back due to some incompatibility they don't address for months.




The biggest pain I've experienced is updating react-router. I've run into cryptic failures each time, and googling usually turns up answers for the previous (or even next/beta) version.


Agreed. It got so bad, that at work I ended up becoming part of the problem and wrote my own isomorphic router for React[0]

[0] https://github.com/studionone/react-isorouter


Babel5/6 too!


the API churn on react-router really tests my patience.


not only that, loss of features like named urls...


Ditto


> My bigger problem has been relying on 3rd party components that hold me back due to some incompatibility they don't address for months.

Welcome to dependency hell :) It happens with all frameworks. The only solution is to use vanilla JS components.


It seems to happen more in the Node world. I can pull down what I need with NuGet for C# and not have too many problems.

Also, reducing the number of external dependencies your project has is always a good idea.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: