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

@michaelfecher/lambda-powertools-http-client

v1.28.1

Published

HTTP client that supports forwarding correlation IDs (captured via @michaelfecher/lambda-powertools-correlation-ids) and auto-records metrics

Downloads

2

Readme

lambda-powertools-http-client

HTTP client that automatically forwards correlation IDs (captured via @michaelfecher/lambda-powertools-correlation-ids), and follows DAZN's convention around recording metrics around integration points.

Main features:

  • auto-forwards any correlation IDs captured with the @michaelfecher/lambda-powertools-correlation-ids package as HTTP headers

  • auto-record custom metrics using the @michaelfecher/datadog-metrics package, which defaults to async mode (i.e. writing to stdout in DogStatsD format) but can be configured via the DATADOG_METRICS_MODE environment variable

  • custom metrics include:

    • {hostName}.response.latency [histogram]: e.g. google.com.response.latency

    • {hostName}.response.{statusCode} [count]: e.g. google.com.response.200

    metric names can be overriden with the metricName option (see below for details)

  • all custom metrics include the tags awsRegion, functionName, functionVersion, method (e.g. POST) and path (e.g. /v1/signin)

  • you can add additional tags by passing them in via the metricTags option (see below for details)

  • supports timeout

Getting Started

Install from NPM: npm install @michaelfecher/lambda-powertools-http-client

API

Basic usage looks like this:

const HTTP = require('@michaelfecher/lambda-powertools-http-client')

const sayIt = async () => {
  const httpRequest = {
    uri: `https://example.com/dev/say`,
    method: 'post',
    body: { message: 'hello world' }
  }

  await HTTP(httpRequest)
}

It's essentially a function that accepts a request of type:

{
  uri/url : string (either uri or url must be specified)
  method  : GET (default) | POST | PUT | HEAD | DELETE | PATCH
  headers : object
  qs      : object
  body    : object
  metricName [optional] : string     // override the default metric name, e.g. 'adyenApi', which changes metrics to 'adyenapi.latency' and 'adyenapi.202'
  metricTags [optional] : string []  // additional tags for metrics, e.g. ['request_type:submit', 'load_test']
  timeout [optional] : int (millis)
}