DEV Community

Ibrahim
Ibrahim

Posted on Edited on

What's your teams' strategy for updating dependencies?

I'm known to be quite OCD about using the latest software available.
And, recently transitioning into web development, I find my OCD fires up a lot with all the tons of npm packages that our apps depend on.

In the teams I've worked at, I haven't seen any solid strategy for updating packages, I find that the vast majority of devs are super afraid of updating dependencies, and they all look at me like I'm crazy if/when I suggest to do something about it.
The result is that we end up with a (functioning) app, that is basically stuck with dependencies on the versions that they were installed with possible vulnerabilities and bugs, outdated ways of doing things.

Am I just super weird, or is there some sort of strategy you all follow with your team's?

Top comments (0)