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

advanced-fetch

v3.1.2

Published

A version of node-fetch with more convenient functionality.

Downloads

29

Readme

advanced-fetch

GitHub license npm Unit tests workflow status

A version of node-fetch with more convenient functionality.

Installation

npm install advanced-fetch

Usage

const { Fetch } = require("advanced-fetch");

(async () => {
  const fetch = new Fetch();
  await fetch.get("http://example.com");
  // subsequent requests to example.com now send the received
  // cookies again, and the cookies are updated automatically
})();

Constructor

The Fetch constructor expects an optional object, with the following possible attributes:

  • cookiesFilename: If given, the tough-cookie cookie jar is serialized into JSON after each request and that JSON is written into the specified file.
  • encoding: If given, the received responses are assumed to be in that text encoding and converted automatically to UTF-8 via iconv-lite before they are returned to you.

Request parameters

Supports .get, .post, .put and .delete. After the URL, all of these functions also expect an optional object with node-fetch request parameters.

Additionally, you can specify the following parameters as normal JavaScript objects, which are serialized respectively automatically:

  • query for GET query parameters, internally serialized using querystring
  • form for the body of a Content-Type: application/x-www-form-urlencoded request, internally serialized using URLSearchParams
  • formData for the body of a Content-Type: multipart/form-data request, internally serialized using form-data
  • json for the body of a Content-Type: application/json request, internally serialized using JSON.stringify

Finally, you can specify returnBuffer: true in the parameters object in order to get a Node.js Buffer as the result of a request instead of a string.

License

MIT