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

le-poste

v0.0.7

Published

a mail wrapper to forget about essential details of life

Downloads

4

Readme

Le Poste

A simple interface to send emails.

code coverage version downloads license

Installation

To install this npm package do

npm i le-poste

Usage

This package is interesting if you are using a dependency injector like di-why, combined with dotenv to just plug the env variables and play. So this will describe usage along with these two packages.

Go to your usual loaders directory index.ts and import mailInjectionDict

// your-project/src/loaders/index.ts
import DiContainer from 'di-why';
// import any other dict elements ...
// and
import { mailInjectionDict } from 'le-poste';

const injectionDict = {
  // somePackageLoadDict,
  // etc.,
  // finally inject all le-poste's loaders into the main loadDict
  ...mailInjectionDict,
};

const di = new DiContainer({ logger, load: injectionDict });
export default di;

Now you can go anywhere in your code and import the index file above:

import di from `./loaders`;
try {
  await di.loadAll();
  const mailSend = di.get('mailSend');
  await mailSend({ subject: "le poste is open", text: "Tu reçois my message" });
} catch (e) {
  console.log('Some error occurred', e);
}

Lots of magic happening here, thanks to di-why and the mailInjectionDict we imported. That's why you need not pass user, password, port and transporter stuff in order to send a message.

A question emerges, how do we pass the connection data to mailSend ? We don't do it directly. Read on.

Passing connection info

In order to configure mailSend, we need to be using dotenv, or add some properties to process.env. They are the following:

MAIL_SMTP_HOST=mail.yourmailprovider.com
MAIL_SMTP_PORT=465
MAIL_FROM_NAME="Jean Jacques"
[email protected]
MAIL_ADMIN_TO_COMMA_LIST="Notify Me Aswell" <[email protected]>
MAIL_TO_COMMA_LIST="Le phare" <[email protected]>
MAIL_PASSWORD='s0meR4nd0mCh4r5'