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

@jsonpages/stack

v1.0.56

Published

JsonPages tenant stack manifest — single source of truth for dependency versions

Downloads

5,497

Readme

@jsonpages/stack

Single source of truth for JsonPages tenant dependency versions (enterprise stack manifest).

Purpose

  • Core syncs its peerDependencies from this manifest (via prepack script).
  • CLI uses this manifest when projecting a new tenant so npm install gets the exact versions defined here.
  • No version drift: one file to change when upgrading React, Vite, React Router, etc.

Workflow

  1. Upgrade stack: Edit stack-versions.json (dependencies, devDependencies, peerDependencies). Keep peerDependencies in sync with what Core supports.
  2. Publish order: Publish @jsonpages/stack first, then @jsonpages/core, then @jsonpages/cli.
  3. From repo: Run npm install at monorepo root so workspace deps resolve; then build/publish Core and CLI as needed.

Consumers

| Package | Use | |----------------|-----| | @jsonpages/core | prepack runs scripts/sync-peers-from-stack.js → copies peerDependencies into Core’s package.json. | | @jsonpages/cli | On jsonpages new tenant <name>, installs deps with name@version from dependencies and devDependencies. |

File layout

  • stack-versions.json — canonical versions (peerDependencies, dependencies, devDependencies).
  • index.js — ESM export for Node (used by Core sync script and CLI).