Packages & Versions

Search the npm registry for packages and see their version, description and install command.

Check the latest version of any npm package, test a version range against all published versions and see install commands.

Check whether versions follow semantic versioning and see their major, minor, patch, pre-release and build parts.

Compare two versions, sort a list, and test whether a version satisfies a range like ^1.2.0 or ~2.3.

Format package.json with the standard key order, sorted dependencies and your choice of indentation.

Fill in a short form and get a ready-to-use package.json with scripts, dependencies and license.

Compare the dependencies of two package.json files and see what was added, removed, upgraded or downgraded.

Work out the next version number — patch, minor, major or pre-release — plus the matching npm and git tag commands.

Write a Keep a Changelog entry from lists of added, changed, fixed and removed items, with compare links.

Create a LICENSE file for MIT, ISC, BSD or Unlicense with your name and year, or a file header for Apache 2.0 and GPL 3.0.

Generate a .npmignore for a library, React component package or CLI so only the files you need get published.

Clean up a Python requirements.txt: normalise names, remove spaces, merge duplicates and sort alphabetically.

Create a composer.json for a PHP package with autoloading, requirements and license.