I usually run ncu to upgrade package.json dependencies to the latest versions.

Sometimes however I want to update to the latest version of a major version, for example I’m on 1.2 and I don’t want to jump to 2.3, I want to stick to 1.3 for example, if it exists.

By default, ncu upgrades the package to the latest version available.

We have the option to only upgrade to minor versions (ignoring major new versions, with breaking changes) with ncu --target minor (or ncu -t minor).

Upgrade only patch versions with ncu -t patch.

I recently also found out about taze. A similar tool.

Use it as taze minor to bump to latest minor changes within the same major version.

Or if you prefer, taze major will check all changes and bump to the latest stable changes including majors.

Patch updates, use taze patch.

Lessons in this unit:

0:	Introduction
1:	How to use or execute a package installed using npm
2:	npm dependencies and devDependencies
3:	How to fix the "Missing write access" error when using npm
4:	npm can install packages in the parent folder
5:	Install an older version of an npm package
6:	Find the installed version of an npm package
7:	How to test an npm package locally
8:	npm global or local packages
9:	What are peer dependencies in a Node module?
10:	`npm run dev` is a long-running program
11:	Semantic Versioning using npm
12:	Uninstalling npm packages with `npm uninstall`
13:	An introduction to the npm package manager
14:	The npx Node Package Runner
15:	The package.json guide
16:	The package-lock.json file
17:	What is pnpm?
18:	Should you commit the node_modules folder to Git?
19:	Update all the Node dependencies to their latest version
20:	Where does npm install the packages?
21:	▶︎ Bumping Node.js dependencies
22:	Run package.json scripts upon any file changes in a folder