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

haddock

v0.0.0

Published

Ha(ddo)ck your API

Downloads

3

Readme

Haddock

Configuration

response: String

Endpoint

Put all response in response folder.

Usage

HTTP response should be placed in a specific folder. HTTP response is identified by :

  • method
  • path
  • body
  • query

A response is place in a file path within method folder. query and body are use to match a HTTP request. Due to filesystem is not a good idea to use query for filepath or filename.

If no extension is provided, it will match HTTP request response type to match with local file mime type.

Path / is match to index filename. Default name is still overridable to avoid conflict. You could override default value to _index or whatever you want.

Ex:

  • GET /foo/bar
  • GET /foo/bar/
  • GET /foo/bar.json
  • GET /foo/bar.xml
  • GET /foo/bar?q=1&w=2
  • GET /foo/bar?q=1&w=3
  • HEAD /
  • POST /foo/bar with body { "username": "alice" }
  • POST /foo/bar with body { "username": "bob" }