Dependencies management: versioning
Published at February 2, 2019 · 2 min read
It’s a really complicated topic. Almost everyone has own opinion on it. I’ll try to describe you several patterns with pros and cons for each.
It doesn’t matter if it’s a python dependency in requirements.txt or a javascript one in package-lock.json file.
What could go wrong? First of all, there are several approaches how dependency could be described:
Case 1: without version
It’s a great approach for development on early stages. You always use the latest version and you’ll be notified soon if your application stopped to work. On the other hand, it’s a nightmare for production deployment. Everything could stop work at any moment after any operating system update.
...