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

backpack-fetch

v0.4.2

Published

A Fetch wrapper utility for use with the Backpack API.

Downloads

12

Readme

backpack-fetch

A Fetch wrapper utility for use with Backpack API.

Basic usage:
import api from 'backpack-fetch';
Example GET request:
const res = await api.get('/books/1234');
if (res.error) return console.log(res.error);
const books = res.data;

The res object returned in the above example is like this:

{
	status: 200,
	data: [ array of book objects ],
	error: null
 }
Example POST request:
const payload = { username: 'billgates', password: 'win95roolz' };
const res = await api.post('/getTokenWithPassword', payload);
if (res.error) return console.log(res.error);
const loggedInUser = res.data;

This time, the res object returned also contains a token (assuming this API route was written to include one).

{
 status: 200,
 data: { user object },
 error: null,
 token: 'abcdefg123456.abcdefg123456.abcdefg123456'
}

Whenever a token is returned, it is automatically saved to the client's local storage as 'token'.

...and whenever a token exists in localstorage, it will always be sent in the HTTP headers along

with every request. For example, the original example api.get('/books/1234') would have included

the JSON webtoken if one existed in localstorage.