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

punchcard-request

v1.4.0

Published

API Request helpers for Punchcard APIs

Downloads

23

Readme

Punchcard Request Build Status Coverage Status

Installation

npm i punchcard-request --save

Usage

Punchcard Request can either be used to make a single request or make a collection of requests to a Punchcard API. A single request is an object with and endpoint specified, with optional configuration and API options. To make multiple requests, collect all desired single requests in to an array. Single requests return as an object, collections of requests are returned as an array.

const request = require('punchcard-request');

const items = [
  {
    get: 'all',
  },
  {
    get: 'types',
  },
];

request(items).then(results => {
  console.log(results); // Array of paginated content and paginated content types available
});

Options

Endpoints

All endpoints are options of the get parameter. Some endpoints require an additional parameter for clarity. These parameters are required.

  • all - All content available
  • types - All content types available
  • type - All content of a specific content type. Requires an additional type parameter for the content type
  • one - A single piece of content. Requires additional type and id properties for the content type and content ID

Configuration

  • punchcard - The URL to the root of the Punchcard install. Can also be set by setting a PUNCHCARD environment variable.

API Options

  • sort - API attribute to sort on. Can be one of id, type, type-slug, key, key-slug. Defaults to key
  • dir sort_dir - Sort direction, can be one of asc or desc. Defaults to asc
  • page - The page to request (for pagination). Defaults to 1, starts at 1
  • limit per_page - The max number of items to return per page (for pagination). Defaults to 30
  • key - Content key that you would like to filter the request for. Only works with all and type endpoints
  • slug key_slug - Content key_slug that you would like to filter the request for. Only works with all and type endpoints