Thanks a lot Ben ! Great talk.

Thanks a lot Ben , I am indeed using semver so this makes a lot of sense. Unfortunately, it seems the video link is down? — I was looking forward to check it out. One of my concerns about increasing those numbers, was to see that huuuuuge list of versions under a npm info package-name . But as Sebastian mentioned, as long as you have well-written tests and builds are green, this probably relates to a good thing. I guess this may also be extended onto another topic which is making sure to create tests for your application from day one . This is something I only recently started to understand and apply and have to say that it indeed takes most (if not all) of the pressure out of releasing new versions of your applications. Otherwise, it can be a shot in the dark and you may keep releasing patches of patches, falling into an infinite loop. Additionally, I stumbled upon this insightful article from Stephan Bönneman , giving good pointers on how to use dist-tags to distribute packages under alternative channels in a way users can help to provide feedback by installing your package under npm install awesomepackage@next . Thanks again for the semver tips that serve as a reminder which is that it's there for a reason, and it's to be used.