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

@saacms/admin

v0.1.9

Published

**Status: placeholder (v0.1.0).** This package is intentionally empty.

Downloads

1,394

Readme

@saacms/admin

Status: placeholder (v0.1.0). This package is intentionally empty.

The full admin UI scaffold lands in a follow-up implementation pass. When it does, this package will become a Vite + React 19 application that ships as the single editor experience across every host adapter (per ADR 0017: "the admin UI is React + shadcn (Puck-driven), regardless of host").

Planned shape

The follow-up will introduce, roughly in this order:

  • Vite + React 19 project, bundled into the host's build output and mounted at /admin/[[...slug]] (or each host's equivalent route).
  • shadcn/ui as the component primitive layer for the app shell, dialogs, forms, and Performance / Cache-debug tabs.
  • Puck as the visual block-tree composer for Pages and templates (per ADR 0004 dual-mode authoring).
  • Monaco as the lazily-loaded power-user fallback for raw Page-JSON, Block-prop, and Collection-schema editing (per ADR 0022 §D5).
  • Better Auth UI wrapped for the sign-in / multi-provider OAuth flow (per ADR 0022 §D4).
  • Floating dev launcher injected into the user's running site in dev mode so the editor opens as an overlay over the current page rather than forcing a navigation to /admin (per ADR 0022 §D2; adopted from Nuxt Studio).
  • Iframe-free real-time preview — the editor's preview pane is the production render path itself, via ADR 0004's preview-fetch + DOM-teleport (per ADR 0022 §D3).
  • Editor UI internationalisation wired from day one even though content i18n is deferred per ADR 0016 (per ADR 0022 §D7).

What's here today

Only src/index.ts with a marker constant and a adminMountInfo() function that reports { route: "/admin", status: "placeholder" }. This exists so that the monorepo's project-references graph resolves and tsc --build stays typecheck-clean while we sequence the real UI work.

No React, shadcn, Puck, Monaco, or Better Auth dependencies are pulled in yet — they land alongside the actual implementation.

Related ADRs