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

batch-endpoint

v0.0.2

Published

A restify plugin for batch-querying `GET` endpoints.

Downloads

8

Readme

Restify batch endpoint

Build Status Coverage Status NPM version

An endpoint for batch-querying GET endpoints on a restify server.

Usage

Once setup, you'll be able to do the following call:

GET /batch?pages=/&pages=/page1&pages=/page2

And receive the following response:

{
    "/": "result from / call",
    "/page1": "result from /page1 call",
    "/page2": "result from /page2 call",
}

When an error occurs in one endpoint, HTTP status code is piggybacked to the main request, and an errored key appear with the invalid page. All other pages will still be loaded.

Implementation

var restify = require('restify');
var batchEndpoint = require('batch-endpoint');

// Initialize server
server = restify.createServer();
server.use(restify.queryParser());

server.get('/endpoint', handlerFunction);
// ... other routes...

server.get('/batch', batchEndpoint(server));

Parameters

require("batch-endpoint") takes two parameters:

  • server, the restify (or HTTP) server to use for GET queries. This parameter can be lazy loaded (wrap it in a function which return the server) to avoid circular dependencies in some use-cases.
  • options, a configuration hash with the following keys:
    • maxPages: page limit per queries. Default to 9.
    • concurrency: internally, the number of calls to do simultaneously to generate the query. Default to maxPages
    • forwardAuthorizationHeader: whether all queries should forward the Authorization header sent to the batch endpoint.