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

leadconduit-integration

v0.6.3

Published

A Node.JS utility module for building LeadConduit integrations

Downloads

9,633

Readme

LeadConduit Integration

A Node.JS utility module for use in LeadConduit integrations.

Build Status

HttpError

When building inbound integrations, you can throw an HttpError in your request function if you want to stop processing the request and respond back to the caller immediately.

The HttpError constructor takes three parameters:

  • status — the HTTP status code to return
  • headers — an object containing the HTTP headers
  • body — a string containing the response body to return

Example

HttpError = require('leadconduit-integration').HttpError

request = (req) ->

  # ensure supported method
  method = req.method?.toLowerCase()
  if method != 'get' and method != 'post'
    throw new HttpError(415, { 'Content-Type': 'text/plain', Allow: 'GET, POST' }, "The #{method.toUpperCase()} method is not allowed")

  # ... carry on with the request function

Test Helper

Use the type parser when building tests to simulate the data that LeadConduit will pass to your outbound integration.

Given an array of request vars, each with a name and type property, the parser will return a function to parse a variables object into richly typed properties. If a request variable isn't provided or if the type cannot be resolved, then the variable is left untouched.

Example

parser = require('leadconduit-integration').test.parser

requestVars = [
  { name: 'zip', type: 'postal_code' }
  { name: 'home_phone', type: 'phone' }
]

parse = parser(requestVars)

parse(name: 'Alex', zip: '78704', home_phone: '5127891121')

# => { name: 'Alex',
#      zip:
#        { [String: '78704']
#          raw: '78704',
#          country_code: 'US',
#          code: '78704',
#          zip: '78704',
#          four: null,
#          valid: true },
#      home_phone:
#        { [String: '5127891121']
#          prefix: '1',
#          raw: '5127891121',
#          area: '512',
#          exchange: '789',
#          line: '1121',
#          number: '7891121',
#          extension: null,
#          country_code: 'US',
#          type: null,
#          valid: true } }