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 🙏

© 2025 – Pkg Stats / Ryan Hefner

trivial-api

v0.0.18

Published

An API handler module with trivial capabilities.

Readme

Trivial API interaction

WARNING alpha version. Do not use!

Very thin utility wrapper around fetch(). Returns Promises.

Current limitations

  • Only works with APIs that expect and return JSON.
  • Only handles authentication by bearer token, which is sent in headers.

Usage

Typical example:


api.write({ url:url, data:data })
  .then(
    (response) => { ...success... },
    (response) => { ...failure...
      throw new api.error("That didn't work!")
  }).then((x) => { 
    ...do something with x...
  }).catch((e) => {
    if (e.isTrivialApiError) {
      ...this is something you threw above using api.error...
    } else {
      ...some other error...
    }
  })

By default, api.error() automatically logs to console.error(). Silence this by calling it with an object: { message: "...", logging: false }

This object expects keys message and, optionally, logging. However, any other key:value pairs can be added too. These can be accessed like so:

let e = new api.error({message: "Some message", someKey: "some value"})
console.log(e.get.someKey)

Certificate errors

If you encounter certificate errors when using Node, you can try setting the environment variable NODE_EXTRA_CA_CERTS appropriately. This ensures Node is aware of certificates you may be using in your local web-server. For example:

sudo NODE_EXTRA_CA_CERTS=/etc/letsencrypt/live/path-to-your-certificates/chain.pem node your-script.js

This great tidbit comes courtesy of https://www.npmjs.com/package/ssl-root-cas