{}

package.json Generator

LOCAL · Browser-Only

Generate valid package.json files with presets, validation, and exports builder

Template

Import an existing package.json to edit

Required

Package Name

Version

Description

Main Entry

Module (ESM)

Types

Bin

Files (comma-separated)

Type

Private

Side Effects

Package Manager

Workspaces (comma-separated)

Quick-add common scripts:

Exports

Define conditional exports for ESM/CJS dual-package support.

No exports defined.

Dependencies

No entries yet. Click Add to start.

Dev Dependencies

No entries yet. Click Add to start.

Peer Dependencies

No entries yet. Click Add to start.

name: Package name is required

description: Missing description - recommended for discoverability

keywords: No keywords - helps npm search find your package

repository: Missing repository URL - recommended for published packages

package.json

{
  "version": "1.0.0",
  "license": "MIT"
}

·Share recipe

Was this tool helpful?

What is package.json Generator?

Generate complete package.json files using a guided form-based builder.

Fill in all standard fields including name, version, description, scripts, dependencies, author, license, repository, exports, and engine requirements. Start from 8 project presets: blank, Node.js CLI, React library, Next.js app, Express API, TypeScript library, monorepo root, and VS Code extension. Validates package names against npm rules and versions against semver. Real-time JSON preview with syntax highlighting. Import existing package.json files to edit. All processing runs in your browser.

How to Use package.json Generator

1Select a project preset or start from blank
2Fill in the form fields - name and version are required
3Add scripts, keywords, and configure engine requirements as needed
4Copy the generated package.json or download it as a file

Frequently Asked Questions

What project presets are available?

Eight presets: Blank, Node.js CLI tool, React library (with peer dependencies), Next.js app, Express API, TypeScript library (with ESM/CJS dual package exports), Monorepo root, and VS Code extension.

Does it validate the package name?

Yes. Package names are validated against npm rules: lowercase, no spaces, no special characters except hyphens and dots, and scoped names must match @scope/name format.

Can I import an existing package.json?

Yes. Upload or paste an existing package.json file and the form will populate with all its values for editing.

Does it support the exports field?

Yes. The exports field builder lets you configure modern ESM/CJS dual package entry points with proper conditional exports for import and require.

How is this different from running npm init?

npm init asks a fixed set of questions in the terminal and produces a minimal file. This builder is a full form covering every standard field including scripts, exports, engines, and repository, with live validation and presets, so you can craft a complete package.json without memorizing the schema.

Are name and version the only required fields?

Yes. A valid package.json only needs name and version, and both are validated as you type. Everything else, including scripts, dependencies, and metadata, is optional and can be added when you need it.

Share this tool

Related Tools

🚫

.gitignore Generator

Generate .gitignore files for any project - 50+ templates for languages, frameworks, IDEs, and OS

{ }

Json schema from json

Free online JSON schema generator - generate JSON Schema from sample JSON data automatically

🤖

Search engine crawler control

Free online robots.txt generator - generate robots.txt files to control search engine crawler access

📝

Env validator

Edit and validate .env files online - detect duplicates, mask secrets, generate .env.example

📋

Keep a changelog

Generate changelogs in Keep a Changelog format - version entries, semver, and diff links

🐳

Docker multi-stage build

Generate production-ready Dockerfiles for 18 stacks - multi-stage builds, best practices included

⚙️

Ci cd generator

Free online github actions generator - generate CI/CD workflow YAML files from templates

$..

Json path

Free online JSON path finder - navigate JSON and click to copy the path to any value

Keep reading: JSON Syntax Cheat Sheet and .gitignore templates reference. Doing this in code instead? See the JSON and data endpoints.

What is package.json Generator?

Generate complete package.json files using a guided form-based builder.

Frequently Asked Questions

What project presets are available?

Eight presets: Blank, Node.js CLI tool, React library (with peer dependencies), Next.js app, Express API, TypeScript library (with ESM/CJS dual package exports), Monorepo root, and VS Code extension.

Does it validate the package name?

Yes. Package names are validated against npm rules: lowercase, no spaces, no special characters except hyphens and dots, and scoped names must match @scope/name format.

Can I import an existing package.json?

Yes. Upload or paste an existing package.json file and the form will populate with all its values for editing.

Does it support the exports field?

Yes. The exports field builder lets you configure modern ESM/CJS dual package entry points with proper conditional exports for import and require.