Skip to main content
Back to Dev generators

Dev

Fake package.json Generator

Used by developers, writers, and creators worldwide.

A fake package.json generator produces realistic package.json files for testing, demos, tutorials, and documentation. The package.json is the manifest at the heart of every Node.js and JavaScript project, and you often need a believable one — to illustrate a tutorial, test a tool that parses manifests, or scaffold an example without hand-writing the fields. This generator gives you a well-formed manifest with a name, version, scripts, dependencies, and the other fields a real project carries, ready to copy into a file or a doc. Because it follows the real structure, it works as a teaching example, a parser test fixture, or a starting point you adapt to your project. Because it runs instantly in your browser for free, you can generate as many manifests as you need, in different shapes, with no cost, signup, or limit on how many you produce.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Select the project type that matches your use case (Express API, React app, CLI tool, etc.) from the dropdown.
  2. Choose whether to include dev dependencies — select 'yes' for a full project setup or 'no' for a runtime-only manifest.
  3. Click the generate button to produce a complete, formatted package.json with dependencies, scripts, and metadata.
  4. Review the output, then copy it using the copy button and paste it into your project, fixture file, or documentation.

Use Cases

  • •Illustrating a package.json in a tutorial or article
  • •Testing a tool that reads or validates manifests
  • •Scaffolding an example project structure
  • •Demonstrating dependencies and scripts in documentation
  • •Generating a realistic manifest fixture for tests

Tips

  • →If you are generating fixtures to test a dependency parser, run the generator several times with different project types to get varied package names and script shapes.
  • →For tutorial screenshots, set includeDevDeps to 'yes' so the dependencies object looks like a realistic project rather than a stripped-down example.
  • →After copying the output, do a quick search-replace on the placeholder author and repository URL — it makes demo repos look much more convincing without any manual JSON editing.
  • →CLI tool outputs produce a bin field in the JSON, which is useful if you need to test tooling that specifically handles executable package configurations.
  • →Cross-reference the generated version numbers against npmjs.com for any packages you plan to keep in a real project — most are close but may lag a major version behind.

FAQ

what is a package.json file

A package.json is the manifest file at the root of a Node.js or JavaScript project. It records the project name and version, its dependencies, and scripts like build and test, plus metadata. Tools read it to install packages and run tasks, which is why a realistic example is useful for testing and teaching.

is the generated package.json valid

It follows the real structure with the standard fields a project carries, so it works as a teaching example, a parser fixture, or a starting point. Adapt the name, dependencies, and scripts to your actual project before using it for real, since the values are illustrative.

what fields does a package.json need

At minimum a name and version, but most include scripts, dependencies, devDependencies, and metadata like description and license. The generated manifest includes these common fields so it reads like a genuine project file, which you can trim or extend to match your needs.