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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fluent-mailto

v1.0.2

Published

A fluent, immutable library for creating mailto links without the hassle

Downloads

147

Readme

fluent-mailto

A fluent library for creating mailto links in javascript.

Testing

  • npm test

Build

  • npm run build

Problem statement

I couldn't find any libraries that made it simple to define mailto links in javascript code.

For example, when asked to add a mailto link with prepolated data in a react component, no one wants to reinvent the wheel:

  1. conditionally combining receipients, body, subject, cc, and bcc with ?
  2. encoding the headers to handle whitespaces, newlines, etc. (i.e. encodeURI and encodeURIComponent)

Furthermore, it can be frustrating either:

  1. Not being able to define a mailto link concisely
  2. Defining a new helper function to abstract this formatting code

Example Usage

fluent-mailto makes it easier to define mailto links in javascript:

Basic

import { mail } from 'fluent-mailto';

...

render() {
	const { recipient, subject, body } = this.props;

	const mailto = mail.to(recipient)
		.subject(subject)
		.body(body)
		.build();

    return (
	    <a href={mailto}>Click here</a>
    );
}

Order agnostic

import { mail } from 'fluent-mailto';

describe('mail', () => {
	it('order does not matter', () => {
		const first = mail.to('example.com').subject('hello world!').build();
		const second = mail.subject('hello world!').to('example.com').build();

		expect(first).toEqual(second);
	});
});

Immutable Builder

import { mail } from 'fluent-mailto';

...

constructor() {
  this.mailtoBase = mail.to('[email protected]').cc('[email protected]');
}

render() {
  const { customers } = this.props;

  return customers
    .map(this.getCustomBody)
    .map((body) => this.mailBase.body(body).build())
    .map((mailto, index) => {
      return <a key={index} href={mailto}>Click here</a>;
    });
}

private getCustomBody(customer) {
  // ... Custom logic
}

Next steps

  1. I haven't conducted performance testing
  2. If you are using strange emails, like [email protected]&[email protected]&body=hello that are technically supported by RFC2368, this library might not be right for you. Need to investigate more how to augment encodeURI or encodeURIComponent to support:
Within mailto URLs, the characters "?", "=", "&" are reserved.

Because the "&" (ampersand) character is reserved in HTML, any mailto
URL which contains an ampersand must be spelled differently in HTML
than in other contexts.  A mailto URL which appears in an HTML
document must use "&amp;" instead of "&".