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

@booleanpress/nimbus-devdocs

v0.1.0

Published

Stripe-style API reference layout and BooleanSMTP-style plugin devdocs widgets, on top of @booleanpress/nimbus.

Readme

@booleanpress/nimbus-devdocs

Stripe-style API reference layout and BooleanSMTP-flavored plugin devdocs widgets, built on top of @booleanpress/nimbus. Consumed today by developers.booleansmtp.com.

What's here

  • layouts/ApiDocsLayout.astro — the three-pane REST API reference shell (nav · content · sticky code rail). Wraps @booleanpress/nimbus's BaseLayout/Header/Footer around components/ui/api-layout's ApiLayout, fetched from @cloudflare/nimbus-docs's component registry (https://nimbus-docs.com/registry) and committed here as owned source, the same distribution model @booleanpress/nimbus itself follows. Needs a real, spec-derived ApiPageProps/ApiNav model — buildApiModel()/getApiPageProps()/getApiNav() from @cloudflare/nimbus-docs/api — it cannot render hand-written prose directly.
  • components/ui/api-layout/, api-sidebar/, api-code-rail/, api-field-row/ — the fetched registry source (ApiLayout, ApiSidebar, ApiCodeRail, ApiFieldRow and their supporting files). One import in ApiSidebarItem.astro was rewritten from a direct file-path import to @booleanpress/nimbus's ui/* barrel (that package only exports whole-folder barrels, not individual files) — otherwise unmodified.
  • components/ui/pro-badge/ — a small Badge variant marking BooleanSMTP Pro-only capabilities. The one genuinely new UI primitive this package adds; everything else it needs (badge, code, banner, breadcrumbs, page-actions, layer-card, sidebar, collapsible) is re-exported from @booleanpress/nimbus's own ui/* via thin shim files at components/ui/<name>/index.ts.
  • lib/cn.ts — a local copy of @booleanpress/nimbus's cn() helper (that package's exports map has no ./lib/cn subpath to import from directly; proposed upstream in office/proposals/).
  • components/HookExplorer.astro, HookSignature.astro, HookParams.astro, WpConfigBuilder.astro — the BooleanSMTP-specific widgets, moved from developers.booleansmtp.com-src. Each takes its data as props now (hooks, signatures, params, scenarios) instead of importing a site-local data module, since a published package can't reach into its consumer's src/.
  • schema.ts (./schema) — devdocsSchemaFields, a sources frontmatter field (the plugin paths a devdocs page rests on) to spread into docsCollection({ schemaFields: { ...seoSchemaFields, ...devdocsSchemaFields } }) alongside @booleanpress/nimbus's own SEO fields. Devdocs-specific — the end-user docs site has no sources convention.

Requirements

Peer dependencies: astro >=7.2.6 <8.0.0, @booleanpress/nimbus >=0.1.1 <0.2.0, @cloudflare/nimbus-docs >=0.15.0 <0.16.0 (one minor ahead of @booleanpress/nimbus's own reviewed 0.14.2 pin — checked safe: nimbus-booleanpress never imports /api or apiCollection(), the only surface that changed between the two versions), tailwindcss + @tailwindcss/vite >=4.1.0 <5.0.0, @iconify-json/ph ^1.2.0.

Using ApiDocsLayout

Not wired to real content yet. It needs an OpenAPI spec (hand-authored for BooleanSMTP, not generated from the plugin's route registrations) parsed through @cloudflare/nimbus-docs/api's buildApiModel() before a route can render through it. Until that exists, REST API content stays on @booleanpress/nimbus's own DocsLayout, the same as every other guide page.