npm-check VS semver

I find this tool helps https://www.npmjs.com/package/npm-check

You can also see npm-check for some more control.

What I do; - run https://www.npmjs.com/package/npm-check with the -u command - select all libs that are relatively safe (minor, patch upgrades) and that are unrelated - upgrade those first and check the app; run it and prod build plus any tests you might have - commit; this is your save point - then upgrade clusters; sets of dependencies that are related (I.e. all test dependencies in one go, all webpack, or all react dependencies in one go) - build, run, test and save again. - Repeat previous two steps until done. - if some dependency requires a major change through the whole app; skip it / revert and safe for another day. Upgrading is sometimes as much about information gathering as it is about upgrading.

I use https://www.npmjs.com/package/npm-check Make a new branch and update all minor (green) in one go, if that's good I commit and move on, then I update all orange in one go, there's usually an issue so then I undo and split that up and do a few each, committing each time it's all ok. Then I do major (red) one by one and commit each time. Some are too hard to update and I'll leave it alone till probably another update fixes the issue.

When I remember the command, sometimes I use npm-check or npm-check-updates to save some time, but I most often don't remember which is the one I usually use and what's the syntax. Yarn has definitely an edge here with its yarn upgrade-interactive command.

Try using `npm-check`: https://www.npmjs.com/package/npm-check

If Dependabot keeps on creating the maximum number of PR's several days in a row, we sometimes just run npm-check update to test and update a bunch of packages at the same time. This is basically the workflow of projects without dependabot and the problem with that approach was that actually nobody was updating the dependencies at all.

Install this package globally npm-check and here is the link link to npmjs.com

npm-check is a useful tool to check for outdated, incorrect, and unused dependencies

Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀

Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.

npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.

We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org

I believe neovim follows semantic versioning. https://semver.org/