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

stub-stub

v0.2.7

Published

Quick and dirty API stubbing mechanism based on YAML files inside a sensible directory structure.

Downloads

8

Readme

stub

stub-stub

npm

stub-stub is a quick and dirty solution to getting your API stubbed out quickly. You can stub out your whole API by simply placing YAML files inside a sensible directory structure.

Installation

Globally:

npm install stub-stub -g

Locally:

npm install stub-stub --save-dev

Getting started

Create an api-stubs directory inside of your project root. Here's an example directory structure:

api-stubs/
├── auth
│   └── default.yml
├── cars
│   ├── 1.yml
│   ├── 2.yml
│   ├── xyz.yml
│   └── default.yml
└── users
    ├── 1.yml
    ├── 2.yml
    ├── 3.yml
    └── default.yml

With the given stubs directory, stub-stub would create multiple endpoints available to you. Some examples include:

| Verb | Endpoint | Returns | | ---- | --------------------|------------------------------------| | GET | / | list all known resources | | GET | /cars | json blob for all cars | | GET | /cars/1 | json blob for car with id 1 | | GET | /cars/xyz | json blob for car with id xyz | | GET | /users | json blob for all users | | GET | /users/2 | json blob for user with id 2 | | POST | /auth/do | default json blob for auth |

stub-stub works by creating endpoints for each YAML file nested within a given type. So for instance, a file at ./api-stubs/cars/1.yml would have a GET endpoint at /cars/1.

Any GET to a given resource extends the default.yml for the given type. You can also POST to any endpoint and receive the corresponding json blob.

Inheritance

Take for instance ./api-stubs/cars/1.yml with the following:

name: Prius
price: $20,000

as well as ./api-stubs/cars/default.yml with the following:

name: Default Car
price: $10,000
mpg: 40

A GET request to /cars/1 would return the merging of default.yml and 1.yml:

{
  "car": {
   "name":  "Prius",
   "price": "$20,000",
   "mpg":   40
  }
}

Starting stub-stub

stub-stub by default starts on port 4343. Why 4343? No idea, it just felt right at the time.

stub-stub

You can optionally run stub-stub on another port and/or from another directory.

stub-stub --port=8000 --stubs=foo

Inflection

Resources are by default pluralized/singularized depending on context using the inflect node module. So, for instance, a GET to /cars will return:

{
  "cars": [
    { "id": "1", "name": "Dodge"}
    { "id": "2", "name": "Buick" }
  ]
}

and a GET to /cars/1 would return:

{
  "car":
    {
    "id": "1",
    "name": "Dodge"
  }
}

Contributing

Fire up a development copy of stub-stub by issuing the following from the command line:

$ ./bin/cli.js

Ticket by Ryan Dell from The Noun Project