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 🙏

© 2024 – Pkg Stats / Ryan Hefner

emeeuw

v0.0.7

Published

The description is to small to describe the aswesomeness of this module

Downloads

5

Readme

emeeuw

Version npmBuild StatusDependenciesCoverage Status

Installation

The module is released in the public npm registry and can be installed using:

npm install --save emeeuw

Usage

In all examples we assume that you have a valid mandrill account and API key as we're a wrapper around their API (but we are more then happy to add more email providers through pull requests).

'use strict';

var Emeeuw = require('emeeuw')
  , emeeuw = new Emeeuw(process.env.MANDRILL_API, { /* options */ });

As you can see in the snippet above we accept 2 arguments:

  1. The API key for the Mandrill API.
  2. An optional object which allows you to specify some messaging defaults:
    • open: Track open of emails, defaults to true.
    • click: Track clicks in emails, defaults to true.
    • subject: Default subject of the emails.
    • from: Default from email address.
    • to: Default to address.

Emeeuw.from

Add a new directory of template sources. It accepts one argument and it should an absolute path to a directory or a filename which points a markdown file.

emeeuw.from('/my/email/directory')
      .from('/path/to/specific/test.md');

The method will walk through the directories and files searching for markdown sources that have a .md extension. If we find markdown files in the first level of the directory we assume that the filename is the name of the template. If we find another directory we assume that the folder name is the name of the template.

For every markdown we assume that there is a file with exactly the same in the folder but with a different extension. The extension can be an extension that is accepted and parsed by Temper. So if you have a foobar.md there should also be foobar.html (or any other extension).

When we are sending the emails we will use the contents of the markdown file as plain/text body of the email. And the rendered result of the template file will be used as HTML body.

Emeeuw.send

After adding template files to your emeeuw instance we can start sending emails. This method requires 3 arguments:

  1. The name of the template you want send
  2. Options to send the message.
  3. Completion callback.
emeeuw.send('example', {
  to: '[email protected]',
  subject: 'My first mass mailing'
}, function (err, resp) {

});

Emeeuw.destroy

Completely destroy the instance so it will release memory of the things it created internally.

emeeuw.destroy();

License

MIT