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

@planningcenter/core-email-editors

v1.0.1

Published

Shared components for rendering email editor form fields across products

Downloads

713

Readme

@planningcenter/core-email-editors

Shared React components for rendering email editor form fields across Planning Center products.

Background

People, Groups, and Registrations each maintain their own email_form component directories for building and editing email content. This package centralizes those components as TypeScript so they can be shared and maintained in one place.

Usage

Install the package in your product and import the components you need from @planningcenter/core-email-editors. You'll also need to import this package's stylesheet once, plus @planningcenter/sweetest-alert's stylesheet (a peer dependency used by Editor.ImageButton's error dialog):

import "@planningcenter/core-email-editors/style.css"
import "@planningcenter/sweetest-alert/style.css"

This package also expects trix and @planningcenter/sweetest-alert to be installed directly by the consuming product (both are peer dependencies), since Trix registers global custom elements and shouldn't be duplicated across bundles.

Local Development

This package uses yalc to test local changes against a consuming product before publishing a release.

  1. Install yalc globally:

    yarn global add yalc
  2. From this package's root, watch for changes and publish them to the local yalc registry:

    yarn dev
  3. From the consuming product, pull in the local version:

    yalc add @planningcenter/core-email-editors && yarn install
  4. If the consuming product's Vite dev setup uses autoBuild (e.g. People's config/vite.json), it decides whether to rebuild based on a digest of its own watched source paths and lockfiles — a yalc publish only touches files inside node_modules, which isn't watched, so the app can keep silently serving a stale bundle after you publish a new local version. Force a rebuild after each publish, e.g. in People:

    devbox run -- bin/vite build --mode development --force

    Plain bin/vite build isn't enough on its own either — without --mode development it builds the production output (public/assets/vite) instead of the dev one (public/vite-dev) that the dev server actually serves.

Testing

yarn test
yarn test:watch

Storybook

yarn storybook