Yea, except I literally never have that problem. Get latest Node and .NET (as an example) and you are good to go after NuGet restore or npm i. Sounds like you g

Yea, except I literally never have that problem. Get latest Node and .NET (as an example) and you are good to go after NuGet restore or npm i. Sounds like you guys need to keep your libraries up-to-date. Which you will need to do anyway if you want your project to be maintainable. On a similar vein - don't pull in every single dependency you can all the time. Btw, this isn't directed at you specifically, obviously, just easier to phrase it that way. Edit: I am actually not arguing just to argue and think about this a lot. A "real world" example is "well, I need to mock out AWS SQS locally and now I have to pull in a fake local queue" or "I need to mock out RabbitMQ locally", etc. The short answer to those things is that you mostly don't - test the endpoint handling queue messages independently / write integration tests for it if you have to. There is no point to having the whole system mocked on your local - SQS/Kafka/whatever will do what it's supposed to do for the most part.