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

200-ok

v1.1.1

Published

A cli http server to fire local requests at that always responds 200 OK.

Downloads

14

Readme

200-ok

A cli http server to fire local requests at that always responds 200 OK.

With cli options can customize status codes for common methods, body reflection, content-type header, and whether to return response body at all.

Pre-requisites

NodeJS, NPM.

Install

npm install -g 200-ok

Using

200-ok

output:

200-ok: listening on port 2000...

Crtl-Break in terminal to stop.

Request Logging

POST /foo
-------------------------------
cache-control: no-cache
postman-token: b54a15a5-121e-49db-b7f1-1e1ad73ae52e
content-type: text/plain
user-agent: PostmanRuntime/7.4.0
accept: */*
host: localhost:2000
accept-encoding: gzip, deflate
content-length: 14
connection: keep-alive
-------------------------------
body: Thisissomedata
len: 14

Type -h at the cli for usage.

Usage: 200-ok [-p port] [--del 200] [--get 200] [--head 200] [--patch 200]
[--post 200] [--put 200] [--content-type text/plain] [--response-body true]
[--reflect-post false] [--reflect-put] false [--reflect-patch] false
[--reflect-all] false [-h]

Options:
-p               port                                      [default: 2000]
--del            DELETE                                     [default: 200]
--get            GET                                        [default: 200]
--head           HEAD                                       [default: 200]
--patch          PATCH                                      [default: 200]
--post           POST                                       [default: 200]
--put            PUT                                        [default: 200]
--content-type   Content-Type for responses        [default: "text/plain"]
--response-body  {"status':"message"} response   [boolean] [default: true]
--reflect-post   Reflect POST body              [boolean] [default: false]
--reflect-put    Reflect PUT body               [boolean] [default: false]
--reflect-patch  Reflect PATCH body             [boolean] [default: false]
--reflect-all    Reflect ALL bodies             [boolean] [default: false]
-h               Show help                                       [boolean]