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

parse-email-address

v0.0.4

Published

Parse/validate email addresses with RFC-5321, and message header address lists with RFC-5322.

Readme

parse-email-address

Parse, validate, and normalize email addresses.

Full docs: https://electrovir.github.io/parse-email-address

Pick the function that matches what you have:

  • One address, like something typed into a form: parseEmailAddress, isValidEmailAddress, normalizeEmailAddress. These accept only user@domain, so Jane Doe <[email protected]> is not valid.
  • A To, Cc, or From header from an email: parseEmailAddressList (any number of addresses) or parseHeaderEmailAddress (exactly one). These accept names, comments, and everything else a header can hold.

This uses and is based on smtp-address-parser v1.1.0, so it has the following features (from smtp-address-parser):

  • Domain names must be fully qualified (they must have at least two labels). The top-level domain must have at least two octets.
  • Total length limit of an address is 986 octets (based on a 1,000 octet SMTP line length).
  • Domain names are limited to 255 octets, when encoded with a length byte before each label, and including the top-level zero length label. So, the effective limit with interstitial dots is 253 octets.
  • Labels within a domain name are limited to 63 octets (limits of the DNS protocol).

This package adds the following features:

  • Full ESM support (this package natively runs in all modern browsers).
  • Documentation.
  • More explicit types.
  • Simplified API.
  • No dependencies.
  • Two different addresses never normalize to the same string. K (U+212A KELVIN SIGN) stays as it is instead of becoming a plain k.
  • IP address domains are checked. name@[IPv6:2001:db8::1] is valid, name@[IPv6:not-an-address] is not.
  • Email header parsing (RFC-5322), including names, comments, groups, line folding, and non-ASCII addresses.
    • A name is never mistaken for an address. [email protected] <[email protected]> has one recipient: [email protected].
    • Unclear addresses are skipped instead of guessed at.
    • A bad address never breaks the rest of the header.
    • Never throws, and safe to run on untrusted email.

install

npm i parse-email-address

usage

import {
    isValidEmailAddress,
    normalizeEmailAddress,
    parseEmailAddress,
    parseEmailAddressList,
    parseHeaderEmailAddress,
} from 'parse-email-address';

/**
 * Parse email addresses into parts with `parseEmailAddress`. Returns `undefined` if the input is an
 * invalid email address.
 */

parseEmailAddress('[email protected]'); // returns `{user: 'simple', domain: 'example.org', full: '[email protected]'}`
parseEmailAddress('[email protected]'); // returns `undefined`

/**
 * Normalize email addresses for string comparisons with `normalizeEmailAddress`. Returns
 * `undefined` if the input is an invalid email address.
 */

normalizeEmailAddress('[email protected]'); // returns `'[email protected]'`
normalizeEmailAddress('[email protected]'); // returns `undefined`

/** Check if an email address is valid with `isValidEmailAddress`. */

isValidEmailAddress('[email protected]'); // returns `true`
isValidEmailAddress('[email protected]'); // returns `true`
isValidEmailAddress('[email protected]'); // returns `false`

/**
 * All three of those implement RFC 5321, the strict envelope grammar, so they accept nothing but a
 * bare `user@domain`. To read a message header, use `parseEmailAddressList`, which implements RFC
 * 5322 and returns every mailbox in the header.
 */

parseEmailAddressList('Jane Doe <[email protected]>, [email protected]');
// returns two mailboxes, the first with `displayName: 'Jane Doe'`
parseEmailAddressList('Intake: [email protected];');
// returns one mailbox with `groupName: 'Intake'`
parseEmailAddressList('undisclosed-recipients:;'); // returns `[]`

/**
 * A display name is never reported as an address, so a display name that looks like an address
 * cannot pass itself off as a recipient.
 */

parseEmailAddressList('[email protected] <[email protected]>');
// returns only `[email protected]`

/** Use `parseHeaderEmailAddress` for a header that should hold exactly one address. */

parseHeaderEmailAddress('Jane Doe <[email protected]>'); // returns one mailbox
parseHeaderEmailAddress('[email protected], [email protected]'); // returns `undefined`