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

sails-hook-email-multi-transport

v0.17.0

Published

Email hook for Sails that allows for multiple NodeMailer transports to be used

Downloads

38

Readme

sails-hook-email-multi-transport

Email hook for Sails JS, using Nodemailer, which allows for multiple Nodemailer transports for sending different types of email though different ways.

Note: This requires Sails v0.10.6+.

Installation

npm install sails-hook-email-multi-transport

Usage

sails.hooks.email.send(template, data, options, cb)

Parameter | Type | Details -------------- | ------------------- |:--------------------------------- template | ((string)) | Relative path from templateDir (see "Configuration" below) to a folder containing email templates. data | ((object)) | Data to use to replace template tokens options | ((object)) | Email sending options (see Nodemailer docs) cb | ((function)) | Callback to be run after the email sends (or if an error occurs).

Configuration

By default, configuration lives in sails.config.email. The configuration key (email) can be changed by setting sails.config.hooks['sails-hook-email-multi-transport'].configKey. The configuration is a single configuration object or an array of objects that look like this:

Parameter | Type | Details -------------- | ------------------- |:--------------------------------- transporters | ((array)) | An array of transporter objects (described below) templateDir | ((string)) | Path to view templates relative to sails.config.appPath (defaults to views/emailTemplates) from | ((string)) | Default from email address alwaysSendTo | ((string)) | If set, all emails will be sent to this address regardless of the to option specified. Good for testing live emails without worrying about accidentally spamming people. testMode | ((boolean)) | Flag indicating whether the hook is in "test mode" globally for all transports. In test mode, email options and contents are written to a .tmp/email-TRANSPORT.txt file instead of being actually sent. Defaults to true. defaultTransporter | ((string)) | The name of the transporter to use if none is specified. useDefaultTransportIfMissing | ((boolean)) | Whether to fall back to the default transport if the specified name does not exist. Note that this generates a warning on the console.

Additionally, if the transporters configuration option does not exist, a new "default" transporter is created by reading the transporter options listed below directly from the config object. This allows backwards compatibility with sails-hook-email.

Transporter Object definition

Parameter | Type | Details -------------- | ------------------- |:--------------------------------- name | ((string)) | The name of this transporter to reference it later service | ((string)) | A "well-known service" that Nodemailer knows how to communicate with (see this list of services) auth | ((object)) | Authentication object as {user:"...", pass:"..."} transporter | ((object)) | Custom transporter passed directly to nodemailer.createTransport (overrides service/auth) (see Other Transports) testMode | ((boolean)) | Flag indicating whether the hook is in "test mode". In test mode, email options and contents are written to a .tmp/email-TRANSPORT.txt file instead of being actually sent. Defaults to undefined which inhertis from the global testMode setting described above.

Example Configuration

// [your-sails-app]/config/email.js
module.exports.email = {
  transporters: [
    {
      name: 'MyGmail',
      isDefault: true,
      service: 'Gmail',
      auth: {user: '[email protected]', pass: 'emailpassword'},
      testMode: true
    }
  ]
};

Templates

Templates are generated using your configured Sails View Engine, allowing for multiple template engines and layouts. If Sails Views are disabled, will fallback to EJS templates. To define a new email template, create a new folder with the template name inside your templateDir directory, and add an html.ejs file inside the folder (substituting .ejs for your template engine). You may also add an optional text.ejs file; if none is provided, Nodemailer will attempt to create a text version of the email based on the html version.

Example of templates

Given the following html.ejs file contained in the folder views/emailTemplates/testEmail:

<p>Dear <%=recipientName%>,</p>
<br/>
<p><em>Thank you</em> for being a friend.</p>
<p>Love,<br/><%=senderName%></p>

executing the following command (after configuring for your email service and turning off test mode) :

sails.hooks.email.send(
  "testEmail",
  {
    recipientName: "Joe",
    senderName: "Sue"
  },
  {
    to: "[email protected]",
    subject: "Hi there",
    transport: "MyGmail"
  },
  function(err) {console.log(err || "It worked!");}
)

will result in the following email being sent to [email protected]

Dear Joe,

Thank you for being a friend.

Love,

Sue

with an error being printed to the console if one occurred, otherwise "It worked!".