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

@leitware/email-templates

v0.1.0

Published

A composable directory of business email templates, best practices, and guides

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

rowanhenrowanhen

Keywords

emailtemplatesbest-practicesmarketingtransactionalcli

Readme

📧 email-templates

A composable directory of business email templates, best practices, and guides. Browse, search, and reference email patterns for any use case.

This is not a code library. It's a curated knowledge base of email templates — what to send, when to send it, what to include, what to avoid, and how to measure success. Use the CLI to navigate and find what you need.

Categories

| Category | Description | |----------|-------------| | onboarding | Welcome emails, verification, onboarding sequences | | transactional | Order confirmations, receipts, shipping notifications | | marketing | Newsletters, product announcements, campaigns | | sales-outbound | Cold outreach, follow-ups, meeting requests | | retention | Win-back, milestones, churn prevention | | billing | Payment failures, cancellations, dunning, refunds | | account-management | Password resets, security alerts, account lifecycle | | support | Ticket confirmations, CSAT surveys, resolution notices | | crm | Check-ins, referrals, review requests | | abandoned | Cart, browse, and form abandonment recovery | | drip-campaigns | ABBA campaigns, nurture sequences, lifecycle automations | | legal-compliance | GDPR, double opt-in, terms updates, unsubscribe | | internal | Employee onboarding, team announcements |

Quick Start

# Install
bun install

# Browse interactively
bun run dev browse

# List all categories and templates
bun run dev list

# Show a specific template
bun run dev show onboarding welcome

# Search across all templates
bun run dev search "payment"

Install Globally

bun run build
npm link
email-templates browse

Template Format

Each template is a markdown file with a consistent structure:

  • Title — what this email is
  • When to Send — triggers and timing
  • Key Elements — what must be included
  • Best Practices — how to do it well
  • Common Mistakes — what to avoid
  • Typical Structure — example layout
  • Metrics to Track — how to measure success

Contributing

  1. Pick a category (or propose a new one)
  2. Create a markdown file following the template format above
  3. Add practical, concise guidance — not verbose essays
  4. Open a PR — all changes require team review

Stack

License

MIT