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

@vouchington/email

v0.2.1

Published

React Email render helpers, style factories, catalog copy loading, and locale resolution.

Readme

@vouchington/email

Pure building blocks for React Email applications. Templates, copy catalogs, brand colors, and locale lists stay in the application and are injected.

react, react-email, and @react-email/render are peer dependencies.

API

  • createEmailStyles({ colors, borderRadius?, fontFamily? }) builds the shared inline styles from caller-owned brand tokens. copyrightYear(now?) returns the year string.
  • emailMessagesFromCatalog(catalog) and loadEmailCatalogMessages(directory) turn @vouchington/localization catalog tables (or a copies.json, aliases.json, translations/<locale>.json directory) into email consumer messages.
  • leavesFromCatalog(messages, locale) resolves messages for one locale with en-US fallback. Applications may instead supply leaves from any other source, such as a SQLite batch.
  • createEmailTranslator(leaves, locale, family) returns a (key, vars) => string translator over email.<family>.<key>. emailOptional picks the .unnamed variant for empty values. formatLocalizationLeaf and interpolate format string, plural, and select-plural leaves.
  • resolveEmailLocale(requested, supported, fallback) matches exact tag, then language, then fallback.
  • renderEmail({ subject, element, text, pretty? }) renders HTML and pairs it with the caller-built subject and plain text.
  • createEmailBundleOptions({ entry, outfile, external?, minify? }) returns esbuild options as data. The application imports esbuild and runs the build.
  • React Email components and render are re-exported for template authors.

Example

const messages = loadEmailCatalogMessages(catalogDirectory)
const leaves = leavesFromCatalog(messages, locale)
const t = createEmailTranslator(leaves, locale, 'welcome')
const result = await renderEmail({ subject: t('preview'), element: <Welcome t={t} />, text })

Caching of leaves, SQLite loading, template sequencing, and sending belong to the application.