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

z-api

v1.0.4

Published

Create an API/Server without having to create the actual server yourself, all you have to worry about is the routes. ## Install ```sh npm i --save z-api ``` ## Usage ```js const Zapi = require('z-api'), api = new Zapi() ```

Readme

Zapi

Create an API/Server without having to create the actual server yourself, all you have to worry about is the routes.

Install

npm i --save z-api

Usage

const Zapi = require('z-api'),
  api = new Zapi()

Add route

const route = {
  method: 'GET', //Default is GET if not specified, Must be in caps
  path: '/', //Default is '/' if not specified,
  handler: (req, res) => {
    /*
    req and res are the standard http objects
    A good guide on how to use them here
    https://nodejs.org/en/docs/guides/anatomy-of-an-http-transaction/
    */
    res.end('The api works)
  }
}

api.addRoute(route)

Remove route

api.removeRoute('GET', '/') //Method and path

Options

Options can be passed set when initialising the class, or they can be set later on.

On initialisation

api = new Zapi({
  port: 80
})

After initialisation

api.config.port = 80

Used options

The following are config options that are currently used, more may be added in the future.

port

The port to run the server on, the default is 3002.

port: 3002

defaultRoute

The default route options to use if that option is not specified. The default method is GET. The default path is '/'. The default handler sends a response saying 'Default route'.

defaultRoute: {
  method: 'GET',
  path: '/',
  handler: (req, res) => {
    res.send('Default route')
  }
}

Middleware

Middleware is run in parallel for the best performance. To add middleware use the addMiddleware function.

api.addMiddleware((req, res, next) => {
  console.dir(req)
  next()
})