The easiest package.json updater there is

Update dependency ranges, tidy your manifest, and create a reviewable diff without leaving your browser.

01Choose the version policy

02Keep your dependency order tidy

03Review before you commit

A better maintenance loop

Less hunting. More shipping.

Everything the updater does is designed to make a small maintenance task stay small.

{ }

Paste once

Bring in the manifest you already have. No repository connection or setup wizard needed.

↗

Set your policy

Choose latest, newest, or next, then decide how conservative each semver change should be.

✓

Review the diff

See what changed, copy the clean result, and keep the final decision in your hands.

From the blog

Dependency updates without the drama.

Practical notes for keeping package manifests healthy, readable, and easier to review.

Read the blog

MAINTENANCE6 min read

A safer way to update every package in package.json

A repeatable checklist for moving quickly without turning a routine update into a risky merge.

Read article

Need to know

Questions, answered.

Everything you need to make your next dependency update feel routine.

Where is my package.json file?

Your package.json file is usually in the root directory of your javascript/typescript/node project. If you have a monorepo pattern (multiple projects in the same repository) you might have multiple package.json files that all need to be updated independently

What format is my package.json file?

Your package.json file is json as expected, but also has several required and several recommended fields. Required fields: name, version. Recommended fields: dependencies, scripts, author, private, license. For more information see https://flaviocopes.com/package-json

What does semver mean?

Semver is semantic versioning. Versions are split into 3 numbers major.minor.patch (e.g. 1.2.3) Usually the first character is either ^ ~ or nothing. ^ means compatible within the minor version (e.g. ^1.2.3 will match 1.2.3, 1.2.4, and 1.3.0, but not 2.0.0) ~ means compatible within the patch version (e.g. ~1.2.3 will match 1.2.3 and 1.2.4, but not 1.3.0) Nothing means exactly that version (e.g. 1.2.3 will only match 1.2.3)

What does * mean?

* means any version is acceptable. Usually this is not what you want, and you should use a specific version or compatible version range instead.

Why should I update my package.json file?

Updating your package.json file regularly helps ensure you have the latest bug fixes, security patches, and new features from the packages you depend on. However, you should test your application after updating to make sure everything still works correctly.

How often should I update my dependencies?

It depends on your project, but a good rule of thumb is to check for updates monthly or quarterly. For security updates, you should update as soon as possible. For major version updates, take more time to test and ensure compatibility.