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

encharge-request

v2.0.11

Published

A zapier-inspired fetch modification.

Downloads

381

Readme

This module implements a Zapier-inspired node-fetch modification.

Usage:

const { request } = require("request");
// Note: Only the URL is required.
request("https://example.com", {
  method: "POST",
  // Set headers
  headers: {
    "X-Header": "Heads up"
  },
  // You can add query parameters:
  params: {
    key: "will be added as a query parameter"
  },
  // Send the body as string
  body: "Can be a string",
  // Or as JSON (sets the Content-Type header to application/json)
  json: {
    Winter: "Fell"
  },
  // Or Form encoded (sets the Content-Type header to www-x-form-urlencoded)
  form: {
    John: "Snow"
  },
  // And other options:
  follow, // max redirect count, 0 for no limit.
  compress, // set to false to disable gzip content encoding.
  timeout, // Request timeout. Set to 0 to disable. Default 0.
  size // Request size limit. Set to 0 to disable. Default 0.
});

Then response is a promise with the following structure:

{
  status, // HTTP status code
    headers, // Response headers as a dict
    content, // Response as text
    json, // Response parsed as JSON, if possible.
    request, // Options object (see above that fired the request).
    getHeader, // Helper function to get header by name.
    throwForStatus; // Helper function that throws if the status > 300.
}