My FeedDiscussionsHeadless CMS
New
Sign in
Log inSign up
Learn more about Hashnode Headless CMSHashnode Headless CMS
Collaborate seamlessly with Hashnode Headless CMS for Enterprise.
Upgrade ✨Learn more

How do you architect your project to cater to changes in frameworks and libraries?

Abinav Seelan's photo
Abinav Seelan
·Dec 11, 2017

For example, when react-router moved to v4, there was a significant paradigm shift in the way react-router worked. If your application was heavily invested in react-router, migrating to v4 was a painful experience.

PS - I don't mean to call out react-router here. I ❤️ v4 and the work that they are doing. Just highlighting a scenario that I've run into. 😄