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

@pantheon-systems/puck-css

v0.20.1

Published

Puck editor integration with Pantheon's P1 content platform

Readme

@pantheon-systems/puck-css

React editor SDK that connects the Puck visual page builder to Pantheon's P1 content platform — real-time multiplayer editing, versioning, remote datasources, and a Pantheon-styled inspector.

Part of Pantheon's P1 platform. It is published publicly so P1 applications can install it, but it is built against Pantheon-hosted services and is not a general-purpose Puck add-on. Pre-1.0: minor versions may carry breaking changes.

Install

npm install @pantheon-systems/puck-css

Peer dependencies you must install alongside it:

npm install @puckeditor/core @tanstack/react-query react react-dom \
            @pantheon-systems/pds-toolkit-react

Most applications consume this through @pantheon-systems/p1-next-sdk, which wires the routes, handlers, and providers for Next.js. Reach for puck-css directly when you are building the editor surface yourself.

Usage

useP1Editor is the primary entry point. It loads the document, joins the collaborative session, and returns props to spread onto Puck:

"use client";

import { useP1Editor } from "@pantheon-systems/puck-css";
import { Puck } from "@puckeditor/core";
import config from "./puck.config";

export function Editor({ path }: { path: string }) {
  const { loading, error, puckKey, puckProps } = useP1Editor({
    documentPath: path,
    puckConfig: config,
  });

  if (loading) return <p>Loading…</p>;
  if (error) return <p>{error.message}</p>;

  return <Puck key={puckKey} {...puckProps} />;
}

It must render inside the P1 providers (P1PuckProvider and a react-query provider); the Next.js SDK sets these up for you.

Stylesheets are shipped separately and need importing once:

import "@pantheon-systems/puck-css/styles.css";
import "@pantheon-systems/puck-css/pds/styles.css";

Entry points

| Import | Contents | | --- | --- | | @pantheon-systems/puck-css | useP1Editor, providers, editor hooks and components | | .../config | Puck config helpers | | .../fields | Field builders, including richtext and inline text | | .../connectable | Connectable HOC for datasource-driven blocks | | .../routes | Route and page-path helpers | | .../utils/path | Document path normalization | | .../server | Server-side helpers (Node runtime) | | .../registry-sync | Component registry sync used by CI and the editor | | .../auth-gate | Auth gating for editor routes | | .../pds | Pantheon Design System wrappers | | .../styles.css, .../pds/styles.css | Required stylesheets |

Documentation

Guides and API detail live with the P1 platform documentation. This README covers installation and the primary entry point only.

License

MIT