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

@ermtech/http-response

v1.0.2

Published

Helper functions realted to Http respsones

Downloads

1

Readme

@ermtech/http-reponse

Creates a properly formated http respsone that can be passed to the Azure Functioons context.res object


API

httpResponse([status],[body],[detail],[headers])

Creates a http respsone formated as per the ERM Tech spec.

  • status number | string - The status code of the response
  • body string | object - The body of the reponse
  • detail string | object - Additional details for error message types
  • headers object - Headers that will override the default { 'Content-Type': 'application/json' } header

Return a non-error type body with the passed body string


context.res = httpResponse(200, "I'm the passed body string")
{
    "status": 200,
    "headers": {
        "Content-Type": "application/json"
    },
    "body": {
        "message": "I'm the passed body string"
    }
}

Return a non-error type body with the passed body object

context.res = httpResponse('OK', { data: "I'm the passed body" })
{
    "status": 200,
    "headers": {
        "Content-Type": "application/json"
    },
    "body": {
        "data": "I'm the passed body"
    }
}

Return a error type body with the passed body and detail passed as a string

context.res = httpResponse('Bad Request',
  'The body must include a queue or topic',
  'A message needs a destination, this is set by the queue or topic name'
)
{
    "status": 400,
    "headers": {
        "Content-Type": "application/json"
    },
    "body": {
        "error": {
            "timestamp": "2021-12-19T06:39:53.181Z",
            "status": 400,
            "type": "Bad Request",
            "title": "The body must include a queue or topic",
            "detail": "A message needs a destination, this is set by the queue or topic name"
        }
    }
}

httpResponse.isErrorCode(status)

Determine if the provided status is a http error code.

  • status number | string - The status code to be evaluated

Check if the status code is an error

httpResponse.isErrorCode(200)
false

httpResponse.isErrorCode('OK')
false

httpResponse.isErrorCode('Bad Request')
true

Build and Test

To publish a new version of this package to npm, run npm run publish:public. You can also dry run the publish with npm run publish:dry. Both scripts with run eslint --fix index.js prior to the publish event just to be safe.