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

@atlaxt/to-public

v3.0.0

Published

Reads package.json and writes a sanitised, public-safe meta.json to your public folder

Readme

@atlaxt/to-public

Reads your package.json and writes a minimal public/meta.json automatically before every build.

Default output:

  • version
  • buildDate

Optional output:

  • dependencies (string array with package names only, no version values)

Setup

npx @atlaxt/to-public

That's it. First run opens an interactive config panel in your terminal. Configure, hit Enter, and the file is generated.

This command also:

  • Adds @atlaxt/to-public to devDependencies (if not already there)
  • Adds "prebuild": "to-public" to your package.json

From then on, meta.json regenerates automatically before every build.

Config panel

The panel appears on first run (when no config file exists). It lets you set:

| Option | Description | | --- | --- | | outputPath | Where to write the output file (default: public/meta.json) | | includeDependencies | false by default. When true, adds dependency names as string[] |

Settings are saved to to-public.config.cjs in your project root with inline comments. You can also edit it manually:

/**
 * to-public config
 */
module.exports = {
  outputPath: 'public/meta.json',
  includeDependencies: false,
}

Legacy to-public.config.json is still supported.

When running as a prebuild script (non-interactive), the panel is skipped and the file is generated directly using the saved config.

To reopen the panel after setup, run:

npx @atlaxt/to-public --config

Output examples

includeDependencies: false

{
  "version": "1.2.3",
  "buildDate": "2026-04-01T12:34:56.789Z"
}

includeDependencies: true

{
  "version": "1.2.3",
  "buildDate": "2026-04-01T12:34:56.789Z",
  "dependencies": ["react", "zod", "zustand"]
}