Understanding Semantic Versioning with Real World Examples

Semantic Versioning, or semver for short, is one of those systems that's used all the time by JavaScript or Ruby developers (and others) but often not understood. It's one of those systems that just sorta works and you don't have to think about it too much, but it actually helps a lot to take some time and understand what the numbers mean and the implications of updating to a new version.
In this video, I'm going to show some really popular packages being used and updated as a sort of real world example, while still keeping the code itself simple. I'm hoping by doing this you can get a hands on example of what it means to update each version number (Major, Minor, and Patch) and how to troubleshoot breaking changes. Knowing this just gives you a lot more control over your project dependencies, and I think it makes you a better software developer if the ideas are new.
Code Repositories for reference:
github.com/Jimmydalecleveland...
github.com/Jimmydalecleveland...
NPM Semantic Versioning video:
• Semantic versioning an...
Old package lockfile video:
• Should you commit Java...
~~~~~~
00:00 - What we'll cover
01:05 - Explanation of Semantic Versioning
07:48 - Quick project setup and npm commands
15:17 - Minor update example (inquirer)
19:15 - Patch update examples (inquirer)
20:36 - Tilde (~) character example (inquirer)
22:29 - How to see versions of a package
24:06 - Major (breaking change) example (inquirer)
29:44 - Chalk package and a Major update fix example
38:33 - Thinking in a semver mindset
~~~~~~
Follow Jimmy Cleveland's doings:
twitter: / jimmydcleveland
blog: blog.jimmydc.com/
#javascript #npm #semver