I think you can and you should narrow down an ecosystem to a specific subset
of features, practices, and definitions.

In react, there are ways to work differently than recommended still available. But if you tell your team how to work with the code base, you should not have any fundamental problems.

I am sure it's the same with vue and other frameworks as well.

For my team, it would be chaotic in a team of react devs if suddenly, some one starts to use class-based components again, utilize .ts helper files, instead of hooks, or introduces redux again, while the team has committed to context API and react-query while keeping the global state as small as possible.

The framework is always only a toolbox, it's up to the team how to use it, and when to update major versions of it.

CTO @webbar & raion.io | Blogger | CTO-Newsletter | Advocates web-native technologies to become the leading platform for digital businesses

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Adrian Stanek

CTO @webbar & raion.io | Blogger | CTO-Newsletter | Advocates web-native technologies to become the leading platform for digital businesses