> I sometimes browse React projects and look at the import blocks to see if I recognize any of the dependencies; I probably average about ~8%. This is very tru

> I sometimes browse React projects and look at the import blocks to see if I recognize any of the dependencies; I probably average about ~8%. This is very true, not just because of the libraries you don't know yet but also because those you do know are continuously evolving. I've been working in the React ecosystem for about 4 years now. I think constantly keeping an eye on the changing ecosystem, and constantly changing the way you do things where it makes sense, just comes with the territory now. You just have to accept it as a way of working, if you're going to enjoy working with React (and JS generally). Whenever I've locked down dependencies and just got my head down and built stuff for a few months, without fail every time I've looked up I've realised that there are now multiple things in my stack that are 'outdated' and there are some genuinely better ways of doing things (some really are just different and equally good, and it's fine to ignore those) that have evolved and been evaluated and ultimately embraced by the community in parallel in the few short months I've had my head down. To be honest it's what I love about the JS ecosystem in general - it's an environment of continual improvement and blisteringly fast pace of change.