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

@paperboycms/preview

v0.1.4

Published

Framework-agnostic on-page-editing bridge for the Paperboy headless CMS preview iframe — click-to-edit, drag-drop blocks, live patch. Zero runtime dependencies.

Readme

@paperboycms/preview

The browser-side on-page-editing bridge for the Paperboy headless CMS preview iframe. Framework-agnostic, zero runtime dependencies.

It is the single source of truth for the message protocol between the CMS admin (parent window) and a frontend rendered inside the preview iframe — so frontends and the admin can't drift.

Frontend (inside the preview iframe)

Call initPreviewBridge() once, only in preview, and mark your editable DOM:

import { initPreviewBridge } from "@paperboycms/preview";

if (inPreviewMode) {
  const teardown = initPreviewBridge();
}
<h1 data-pb-field="heading">…</h1>
<div data-pb-field="contentarea" data-pb-area="contentarea">
  <!-- each rendered block: -->
  <section data-pb-block-index="0" data-pb-block-type="CardBlock">…</section>
</div>

The bridge then:

  • posts paperboy:edit when an editable region is clicked (with rect/click/caret),
  • posts paperboy:drop when a shared block/page is dragged from the Assets pane onto a data-pb-area,
  • streams paperboy:rect on scroll/resize, applies paperboy:patch (live swap) and paperboy:focus,
  • injects its own styles and persists scroll across reloads.

Admin (parent window) — types only, no DOM

import { parsePreviewMessage, patchMessage, focusMessage } from "@paperboycms/preview/protocol";

parsePreviewMessage(ev.data) narrows an incoming message to the typed union (or null for unknown/garbage — the protocol is additive-only and both ends ignore unknown types, so independently-deployed admin/frontends degrade gracefully).

Attribute contract

| Attribute | Meaning | | --- | --- | | data-pb-field | An editable field region (value = field name) | | data-pb-area | A content area that accepts block drops (value = field name) | | data-pb-block-index / data-pb-block-type | A rendered block inside an area |

⚠️ data-pb-area's value must be the contentArea field name — the bridge posts it back to the editor as paperboy:drop {field}, which looks the field up on the content type. A boolean-ish marker (data-pb-area="true") makes every drop fail; the bridge warns about it in the console. Prefer spreading pbAreaAttrs(field, preview) from @paperboycms/client instead of writing the attribute by hand (it also keeps public pages marker-free).