Introducing Socket Firewall: Free, Proactive Protection for Your Software Supply Chain.Learn More
Socket
Book a DemoInstallSign in
Socket

@zaneray/express-drip-middleware

Package Overview
Dependencies
Maintainers
8
Versions
7
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@zaneray/express-drip-middleware

Handle interactions with nodejs-drip as express middleware

latest
Source
npmnpm
Version
1.0.7
Version published
Weekly downloads
3
50%
Maintainers
8
Weekly downloads
 
Created
Source

Express server Drip middleware

Provides a convention based method to push subscribers to Drip as an Express server middleware plugin.

For now, the only thing it does is exposes a function to collect the req.body details in to a valid batch[] to be submitted to Drip as well as the batch subscribe method that will post the data and either return a helpful error, or call next()

Installation

npm install --save @zaneray/express-drip-middleware

Usage

const express = require('express');
const drip = require('@zaneray/express-drip-middleware');

const server = express();
server.use('/', express.static(__dirname));

async function start() {
  drip.setup(DRIP_ACCOUNT_ID, DRIP_API_TOKEN);
  server.post('/some-endpoint-path', [drip.createUserBatch, drip.submitUserBatch], (req,res) => {
    res.status(200).send({success:true});
  });
}
start();

Expected behavior

CreateUserBatch will iterate over the req.body.drip.subscribers array and validate the data as defined in the method (currently only checks for a valid email) and will then package those up in to the request format expected by the drip-nodejs batch processor and place it back on the request.

SubmitUserBatch will attempt to post that data, and then call next() or call next(err) with a helpful response

Error Response

On an error, it will return an embelished error object that allows you to modify behavior as necessary depending on the error code or message returned.

We have a custom error handler in express that expects these elements to define the actual server response code, and wraps it in a data {} object for consistency in the client view layer.

  • 422 if the createUserBatch function rejects the data
  • 400 if submituserBatch fails to process the data, and is handled in a meaningful way
  • 500 if not
// would be the response if your customers array submitted was empty
{
  message: 'the error message',
  statusCode: 400,
  component: 'refusing to send 0 customers to Drip',
  status: false  
}

FAQs

Package last updated on 04 Jun 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts