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

@saws/email

v1.0.11

Published

<div align='center'>

Downloads

12

Readme

Email

Service and library for sending email in your application.

Table of Contents

Installation

From the command line run:

npm install @saws/email

Then add the included service (EmailService) to your saws.js file.

Development

In development this service does nothing. There is no local infrastructure required for how the library implements email sending.

Any emails sent in development will just be logged to the console.

Deployment

In a deployed environment, email sending is managed by AWS SES. One thing to note is that by default all SES accounts are by default limited to verified domains and emails. So if you'd like to use SES to send to non verified emails, you will need to go through their process to have your account removed from the sandbox.

When you deploy an EmailService no infrastructure is stood up. But any services that depend on an EmailService will have their permissions configured to be able to send emails via SES.

Services

@saws/email has a single service that is includes, EmailService.

EmailService

You can require the EmailService and use it in your saws.js file like so:

const { EmailService } = require('@saws/email/email-service')

// will almost always be used as a dependency to another service
const email = new EmailService({
  name: 'my-email-service'
})

The EmailService constructor accepts the following options:

name: string

The name of your service. This should be unique across all of your services.

dependencies: ServiceDefinition[]

An array of all of the other services this service depends on. This will ensure that permissions, environment variables, and execution order are all set up.

When used as a dependency

When an email service is used as a dependency, it does not inject any environment variables into dependant services.

Libraries

@saws/email a single library for sending email, Email

Email

The Email library is a class that allows you send emails via SES in production, or log to the terminal in development.

Example usage:

import { Email } from '@saws/email/email-library'

const client = new Email()

sendEmail(options: { to: string[]; subject: string; type: "html" | "text"; message: string; source: string; })

Sends an email.