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

@nendlabs/docpage

v0.1.6

Published

an interactive paper-style project page renderer

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

dxededxede

Keywords

Readme

@nendlabs/docpage repo

this repository contains the @nendlabs/docpage package, its playground, and internal docs.

repository overview

key paths:

  • src/: the package source
  • styles/: tailwind entry + theme tokens
  • playground/: local app to preview configs
  • docs/: deeper documentation and publishing notes
  • .github/workflows/: ci and main-branch publishing

npm readme behavior

npm always reads README.md at publish time.

to keep this repo readme maintainer-focused while shipping a package-focused npm readme:

  • docs/package.md is the source of truth for the npm readme
  • prepack copies docs/package.md into README.md
  • postpack restores the original README.md

relevant scripts:

  • bun run readme:package
  • bun run readme:restore
  • bun run build

development

install and run the playground:

bun install
bun run dev

run local validation:

bun run typecheck
bun run test
bun run build

docs

deeper documentation lives under docs/:

  • docs/authoring.md
  • docs/mdx.md
  • docs/publishing.md
  • docs/package.md

release flow

publishing is automated on pushes to main.

high level:

  1. open a pr into main
  2. bump package.json version in the pr
  3. merge to main
  4. ci validates and the publish workflow runs npm publish

see docs/publishing.md for details.