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

validate-response

v1.4.0

Published

Validate http response (for example from scra)

Downloads

15

Readme

validate-response

Validate http response (for example from request, got, scra or needle).

Build Status NPM version

Install

npm i validate-response

Usage

const validateResponse = require('validate-response');

const validator = validateResponse(options);
// //or//
// const validator = validateResponse(...codes);

validator(response);

// validator throws ValidateResponceError if response is invalid, otherwise do nothing.
// also validator throws TypeError if response is not instance of http.IncomingMessage (now disabled).

// validator created without any params will treat every response as valid.

options:

  • codes - valid values for response.statusCode. May be number between 100 and 599, comma-separated string with such numbers or array of all above. Even like this:

    const validator = validateResponse({codes: [200, '300, 400', '500']});

    On invalid codes error will be thrown.

  • checkJSON - boolean, if true error will throws on response that has content-type set to application/json, but has string in body field (not object). Defaults to false.

  • checkType - boolean, if true error will throws on response that is not instanceof http.IncomingMessage. Defaults to false.

  • contentLength - positive number or array of two numbers, means value of response content-length must be equal to number or in range of two numbers. If not (or if response has no content-length header) error will be thrown.

  • bodyMatch - regexp for testing response body string. If body does not match regexp, error will be thrown.

  • validator - custom validator function, that takes response and return truthy value for valid response. If throws or return falsy - error will be thrown. It makes no sense to use this function if other options are not specified.

If response is invalid by many reasons error will be thrown only once and all reasons will be listed in reasons field.

codes:

If first parameter of validateResponse is not object all parameters are codes. Each parameter has same schema as codes option`. It may looks even like this:

const validator = validateResponse(200, '300, 301 , 302 ,307', ['400', '401, 403', 451], '500']});

But usually it looks like this:

const validator = validateResponse(200);

ValidateResponceError:

On bad responce validator throws ValidateResponceError, that has some useful additional fields:

  • reasons - array of human readable text messages describing the reasons why ValidateResponceError was thrown. If there is only one reason, that will no reasons field and that reason message will placed in message field of error object.
  • codes - array of sort text codes for corresponding reasons. Every code is one of 'E_INVALID_STATUS', 'E_INVALID_JSON', 'E_INVALID_LENGTH', 'E_INVALID_MATCH' or 'E_INVALID_RESPONCE'.
  • url - same field of responce.
  • statusCode - same field of responce.
  • bodyLength - length of responce.body.
  • headers - key-value object with responce headers.
  • cookies - same field of responce.

License

MIT