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

@johnanthonyeletto/mail-to

v1.0.5

Published

mailto: links that don't suck. Detect email provider from MX records and open the right compose URL (Gmail, Outlook, Zoho, Proton) or fall back to mailto:.

Readme

mail-to

mailto: links that don’t suck. Detect a user’s email provider from MX records and open the right compose experience (Gmail, Outlook, Zoho, Proton) or fall back to mailto:.

⚠️ Warning: This library is not battle tested. Use at your own risk. Contributions, bug reports, tests, and improvements are very welcome.

Framework-agnostic. Works in Node and the browser.

Install

npm install mail-to

Usage

Compose (recommended)

Pass a from address and a to; the library looks up the provider and returns a URL you can open (e.g. Gmail compose, Outlook deeplink, or mailto:).

import { compose } from "mail-to";

const url = await compose({
  from: "[email protected]",
  to: "[email protected]",
  subject: "Help",
  body: "Hello…",
});

window.open(url); // or location.href = url

Without from, it returns a plain mailto: URL.

Detect provider only

import { getEmailProvider, EmailProvider } from "mail-to";

const provider = await getEmailProvider("[email protected]");
// EmailProvider.GOOGLE | EmailProvider.MICROSOFT | EmailProvider.ZOHO | EmailProvider.PROTON | null

Uses Google DNS over HTTPS to resolve MX records for the domain and matches against known provider hostnames (e.g. aspmx.l.google.com, *.mail.protection.outlook.com).

Optional: pass provider yourself

If you already know the provider, pass it to avoid a DNS call:

await compose({
  from: "[email protected]",
  to: "[email protected]",
  provider: EmailProvider.GOOGLE,
});

API

| Export | Description | | ------------------------- | ---------------------------------------------------------------------------------------------------------- | | compose(config) | (config: ComposeConfig) => Promise<string> – Returns a compose URL (provider-specific or mailto:). | | getEmailProvider(email) | (email: string) => Promise<EmailProvider \| null> – Resolves MX and returns the provider enum or null. | | EmailProvider | Enum: GOOGLE, MICROSOFT, ZOHO, PROTON. | | ComposeConfig | { from?, to, subject?, body?, provider? }. |

Browser (script tag)

Build outputs a global bundle:

npm run build

Then in HTML:

<script src="node_modules/mail-to/dist/index.js"></script>
<script>
  const url = await MailTo.compose({ from: "…", to: "…" });
  window.open(url);
</script>

Or copy dist/index.js to your project and reference it.

Scripts

| Command | Description | | --------------- | ------------------------------------ | | npm run build | Build ESM, CJS, and IIFE to dist/. | | npm run dev | Build in watch mode. |

Publishing

Releases are published to npm via GitHub Actions when you push a version tag. Publishing uses npm Trusted Publishing (OIDC); no NPM_TOKEN secret is required.

Releasing a new version

  1. Bump the version and create a tag:
    npm version patch   # or minor / major
  2. Push the tag to trigger the workflow:
    git push --follow-tags
    Or push a specific tag: git push origin v1.0.0.

The workflow runs on tag push, builds the package, and publishes to npm.

License

ISC