Often when I'm going through tutorials, the instructor uses very specific version numbers when installing a package using npm, usually the most recent one at the time they made the tutorial. That seems like a reasonable way to do it when making a tutorial, but is that best practice when making a live app? Do you use the most recent one and then over time manually upgrade components?
With newer versions of npm or yarn, it's not a problem thanks to the lock file. Take in consideration that this file must be added to your control version so the team can really take advantage of this feature.
I don’t specify them for most packages. I only do it when I want to use latest for trying a new feature that is recommended by the author, or a for a very specific use case.
Sebastian
Usually I don’t specify them. The only time I had to this was when minor versions contain breaking changes then I have to pin the version. But that happens rarely but it happens.