Build package.json files with scripts, dependencies, metadata, and best-practice defaults.
This tool assembles a package.json file from form fields instead of hand-typed JSON: package name, version, description, entry point, license, author, npm scripts, and a dependency list. Each field maps directly to the matching JSON key, and fields left blank are simply omitted rather than filled with guesses. The most common surprise is dependency versions: the generator does not query the npm registry, so whatever version string you type - including the word 'latest' - is written into the file exactly as entered, with no resolution to an actual published version number.
A concrete input and expected output from the current implementation.
Input
name: weather-cli version: 0.1.0 description: Fetch current weather from the command line main: bin/cli.js license: MIT author: Jane Doe scripts: start = node bin/cli.js, test = echo "no tests yet" dependencies: commander @ ^12.0.0
Expected output
{
"name": "weather-cli",
"version": "0.1.0",
"description": "Fetch current weather from the command line",
"main": "bin/cli.js",
"scripts": {
"start": "node bin/cli.js",
"test": "echo \"no tests yet\""
},
"author": "Jane Doe",
"license": "MIT",
"dependencies": {
"commander": "^12.0.0"
}
} Each form field writes to its corresponding top-level key; repeatable script and dependency rows become nested objects keyed by the name you typed, with the value copied through unchanged.
Each form input corresponds to one package.json key: name, version, description, main, license, and author map one-to-one. Scripts and dependencies are entered as repeatable name/value rows - a script name paired with its shell command, or a package name paired with a version string - which the tool assembles into the matching nested object, preserving the text exactly as typed.
Before rendering output, the tool checks that the package name follows npm's naming rules (lowercase, no leading dot or underscore, URL-safe characters, 214-character limit) and that the version field parses as valid semver. Malformed entries are flagged for correction, but the check is purely structural - it does not confirm the name is unregistered on the npm registry.
No. It only generates the package.json text in your browser; nothing is uploaded or sent anywhere. You copy or download the file, place it in your project, and run npm publish yourself from the command line when you're ready.
No. It doesn't query the npm registry, so it can't confirm a package name is real or that a version string corresponds to a published release. Check availability and current versions with npm view <package> or npmjs.com before relying on the generated file.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.