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

mandrill-node

v1.1.4

Published

A node.js wrapper for MailChimp's Mandrill API.

Downloads

6

Readme

mandrill-node

mandrill-node is a node.js module for interfacing with MailChimp's Mandrill API

###Please Star it on github if you liked it

##Installation

Installing using npm (node package manager):

npm install mandrill-node

If you don't have npm installed or don't want to use it:

cd ~/.node_libraries
git clone git://github.com/akarshsatija/mandrill-node.git mandrill
//Include the mandrill module
var mandrill = require('mandrill');

##Requirements

  • A MailChimp account, Mandrill service enabled, Mandrill API key. See the Getting Started guide for more information http://help.mandrill.com/customer/portal/topics/214457-getting-started/articles
  • node.js 0.8.0+
  • request 2.9.100+
  • underscore 1.3.3+

##Examples

// The key can be set either by passing the a an object which only
// contains the key, ex.
mandrill.call({'key':'mykey'});

/**
 * They key could also be set with the request event. All request events
 * need to have at least a type and a call property set and these values
 * need to correspond to the valid types and calls recognized by the Mandrill
 * service.
 *
 * Here is an example of a call to Mandrill API's users.info
 * The docs for this call can be found at http://mandrillapp.com/api/docs/users.html#method=info
 */
mandrill.call({'type':'users','call':'info'}, function(data){
    console.log(data);
});

// For a list of valid calls please visit http://mandrillapp.com/api/docs/index.html

##Contributions

The Mandrill node.js module is designed to be as static as Javascript allows, following a functional or lambda programming paradigm. If you want to learn more about this pattern of development and why this pattern was chosen above other, more traditional, javascript approaches please read the following excellent article http://howtonode.org/why-use-closure

If you would like to help maintain this project and/or if you have any questions or comments about the library's design or implementation I'd love to hear from you.

##Unit Tests

A unit test using nodeunit for the Mandrill module is avaliable in the 'unit' directory. You will need to copy the configure.json.example to configure.json and change the Mandrill API key from 'mykey' to your Mandrill API key in order for the tests to complete. If you want to contribute any bugfixes or examples please add a unit test for your code and make sure nothing else breaks.