Because 1.17 is out, 1.15 (the last one that worked before the breaking change) no longer matches the version constraints in our file, so if we want it, we'll have to specify the version manually.
So without further ado: Sure, we've all got our methods, but the point of this is to provide something for people who don't know how to use such tools.
In an ideal workflow, you'll really only do this when you need to a package because of a breaking change in the latest release, for example.
I'll explain more about why that is in another video, but let's get to it.
We actually just did this in the last video, but I didn't want to gloss over it, and if you're trying to figure out how to manually update a package, you probably aren't using the dev version.
So, this video will show how to update packages to a specific version.
But as with anything in life that catches up with us, it was inevitable. (My wife spent our first few dates looking at me under the hood, trying to recover from breakdowns that would leave us standing still on cold nights). It died because I didn’t realize the importance of regular upkeep and a frequent changing of oil on appropriate intervals. And with my carefree youthful attitude, I likely wouldn’t have cared. Of course you plan on getting full use of his bad boy!