If the update is within the semver filter you have in your package.json, it’s easy to upgrade with npm upgrade, but if you’re in a situation like I found myself in from the above list, there’s a lot of major version upgrades needing to be done, and since they are beyond the allowed semver range it’s a non-starter. If you want some more information you can provide the -long flag and get more output, such as whether the package is in the dependencies or devDependencies list:
Finding Outdated Packagesįirst off, how do you know what’s outdated? We can use npm outdated for that and it’ll return something like this: That it is over 3 years old, so the content in here may not be accurate.Įver come back to a project you haven’t touched for a while, only to find out there’s a lot of outdated npm packages that you want to update? This is a situation I occasionally find myself in and I’d never thought of a good way to tackle it.
Hey, thanks for the interest in this post, but just letting you know The upgrade -latest command upgrades packages the same as the upgrade command, but ignores the version range specified in package.json.
0 kommentar(er)
