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/blocks-essentials

v0.1.9

Published

**Status:** scaffold (v0.1.0). Not yet wired into a host app.

Readme

@saacms/blocks-essentials

Status: scaffold (v0.1.0). Not yet wired into a host app.

The built-in Block library shipped with saacms. Currently exports the Hero block.

Authoring mode

All built-in blocks are authored as Web Components (Mode 1 per ADR 0004 — Block authoring: dual mode).

Web Components are framework-agnostic by construction: the same <saacms-hero> element renders identically whether the host framework is Astro, Next.js, SvelteKit, or Nuxt. This is why the built-ins choose Mode 1 — one bundle, every host.

Block authors who want host-framework-native ergonomics (React hooks, Svelte stores, scoped CSS) should choose Mode 2 (framework-native) for their own blocks. The built-ins stay portable.

Reactivity

Reactive state inside the Web Components uses the cross-framework signal primitive from @preact/signals-core per ADR 0023 — Frontend state and backend-driven sync. The eventual migration target is the TC39 Signals proposal; the wrapper is a one-line swap.

Usage

import { register } from "@saacms/blocks-essentials"

// Call once at app boot — registers all built-in custom elements.
register()

After registration, the elements are available as standard custom elements:

<saacms-hero
  title="Ship faster"
  subtitle="A CMS that respects your stack."
  cta-label="Get started"
  cta-href="/signup"
></saacms-hero>

Notes on this scaffold

  • No shadow DOM — the Hero component renders into its light DOM for v1 simplicity. This means the host page's CSS reaches in and styles the block, which is the intentional v1 behaviour (matches editor preview ergonomics). Shadow DOM with slotted content is a candidate for a v2 hardening pass once the styling story crystallises.
  • Observed attributes are kebab-case per the HTML standard (title, subtitle, cta-label, cta-href); the block schema uses camelCase (ctaLabel, ctaHref) and saacms's compile step bridges the two.

Known reconciliation TODO

src/hero/Hero.block.ts defines a local BlockDef type. Once @saacms/core's defineBlock is fully exported and the contract test suite locks the shape, swap the local type for the canonical import.