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

@m59/fetch

v0.0.0

Published

Fetch API with conveniences I like.

Downloads

1

Readme

@m59/fetch

Fetch API with conveniences I like.

This is shimmed for server side usage with node-fetch. The server code is ignored when bundling for the browser.

install

$ npm install @m59/fetch

example

const fetch = require('@m59/fetch')

fetch.json({
  url: URL + '/posts',
  query: { userId: 1 }
}).then(({response, body}) => body[0].id) // 1

api

fetch([url], options)

The first argument can be a url or options object. If you pass only an options object, it should have a url property. Put your normal fetch options in options.

options.query

options.query is an object that will be used to create a query string that will set or overwrite the query string in the given url

{
  url: '/foo'
  query: { bar: 123 }
} // => /foo?bar=123

options.body

If you set options.body to an instance of FormData, the form data content type header will be set automatically. If you set options.body to a regular object, it will be JSON stringified and the json content type header will be set automatically.

helpers

If you want the response body in a certain format, save some code by using the corresponding helper. json() and text() will also set the appropriate accept header to ensure the server knows what format you want. The result will be in the format { response, body }.

fetch.arrayBuffer()
fetch.blob()
fetch.json()
fetch.text()
fetch.formData()