We think Postmark and Node.js go together like chocolate and peanut butter. So, just in time for Valentine’s day, we’re snuggling up to Node.js with an officially supported module for Postmark!
In December, we released a huge update to Postmark.Net. Less than a month ago, we released Postmark-PHP , our officially supported client for PHP. But we’re on a quest... A quest to make it super simple to add Postmark to any platform you’re using.
A little less than a month ago, we contacted Chris Williams about sharing ownership of the ‘postmark.js’ module on NPM. Chris was excited to collaborate, and as a result, we’ve made some big improvements that we’d love to share with you.
So, what’s new?
Full API Coverage: Using the updated module, you may send and receive emails, update servers, add/delete sender signatures, create triggers, process bounces, and a whole lot more. Anything you can do with our REST API, you can do with Postmark.js.
Full Integration Test Coverage: Every commit to master is tested against our live API. We’re currently testing on Node.js 0.6, 0.8, 0.10, 0.11, 0.12, and iojs 1.2.0, and 1.2.1.
Easier Unit Testing: In our case, testing Postmark.js against our live REST API is critical in verifying the proper function of the module. For consumers of the module, it is often useful to mock or proxy API requests. We’ve exposed the ’requestFactory’ so that you can intercept Postmark requests during testing.
If you’re already using Postmark.js, fear not, you can continue using the updated module without any changes to your code.
The latest version of Postmark.js is available now, and can be installed easily in the usual way:
npm install postmark --save
We’d like to thank Chris Williams for his graciousness in collaborating with us. Chris’ work (as well as the other contributors’ work), provided a solid foundation from which to work in bringing these improvements to the module.
As always, we hope these enhancements make your life easier. We’d also love to get your feedback on the updated module, it really helps!
This post was originally published Feb 12, 2015