package.json Editor

How to use it

1. Paste a package.json into the top panel and click Load into editor.
2. Edit the core fields: name, version, description and main.
3. Manage scripts as key and value rows — add rows with Add, remove them with the small remove button on each row.
4. Do the same for dependencies and devDependencies; the two lists stay separate so nothing drifts between them.
5. Click Export JSON to build the file. The hint line flags a missing name or version and a version that does not look like semver.
6. Copy or download the result. Fields the form does not manage (license, type, engines and the rest) are preserved exactly as they were.

Common use cases

• Fixing a manifest by hand — correct the name or version without fighting indentation in a text editor.
• Splitting dependencies — move a package from dependencies to devDependencies row by row.
• Adding a script — add a build or test entry and export the file in one pass.
• Reviewing before publishing — read the hint line and confirm nothing required is missing.

Why it stays private

The manifest is parsed and rebuilt in your browser. Nothing is uploaded, no registry is contacted, and dependency versions are never resolved — the tool only rearranges the text you already have.

FAQ

Q: Does it install or update anything? A: No. It edits text only. There is no npm install, no version resolution and no network access of any kind.

Q: What happens to fields the form does not show? A: They are kept as they are and written back on export. Only the managed keys are rebuilt, and empty optional fields are omitted instead of written as empty strings.

Q: Why does the export put my extra fields after the managed ones? A: The output is assembled in a fixed order — name, version, description, main, then untouched keys, then scripts, dependencies and devDependencies. JSON object order does not change meaning, and npm reads the file the same way.

Q: What counts as a version warning? A: The hint checks that the version starts with three numbers separated by dots, like 1.2.3. Pre-release and build suffixes after that are left alone.