npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

package-cjson

v3.0.0

Published

Add comments in package.cjson/package.json.js/package.json.ts in Node JS project; Generate package.json from it; Compare with package.json

Readme

package-cjson

Add comments in package.cjson/package.json.js/package.json.ts in Node JS project; Generate package.json from it; Compare with package.json.

Sources

package-cjson looks for package source file in this order:

  1. package.json.ts
  2. package.json.js
  3. package.cjson

When package.json.ts or package.json.js is present, the default export is used as the contents for the generated package.json.

const dependencyName: string = 'chalk';

export default {
    name: 'my-package',
    version: '1.0.0',
    dependencies: {
        [dependencyName]: '^5.6.2'
    }
};
const dependencyName = 'chalk';

export default {
    name: 'my-package',
    version: '1.0.0',
    dependencies: {
        [dependencyName]: '^5.6.2'
    }
};

The exported value must be JSON-serializable. Output is written with stable key ordering, using the indentation and trailing newline style from the source file.

package-cjson requires Node.js >=24.2.0 (for import.meta.main, used to detect direct CLI invocation). package.json.ts is loaded with Node's native TypeScript support (available since 22.12.0); package.json.js is loaded with Node's native JavaScript module support.

Usage

package-cjson --mode generate-package-json
package-cjson --mode compare
package-cjson --mode generate-package-version-json
package-cjson --mode compare-package-version

The update mode updates dependency versions in the selected source file (package.json.ts, package.json.js, or package.cjson, in that priority order). The update-and-generate-package-json mode performs that update first, then generates package.json from the same source.

Note: Dependencies declared with computed keys in package.json.js/package.json.ts (e.g. [dependencyName]: '^1.0.0') are skipped by --mode update, since the package name does not appear literally in the source file.