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

@xconnortv!/http-status-cli

v1.0.5

Published

Install globaly: ``` npm i -g @xconnortv!/http-status-cli ``` Usage: ``` > http-status l <code> -optional > http-status lookup <code> -optional > http-status <code> -optional ``` Optionals: ``` -s, -short | Short description -p, -plain | Plai

Downloads

2

Readme

http-status-cli

Install globaly:

npm i -g @xconnortv!/http-status-cli

Usage:

> http-status l <code> -optional
> http-status lookup <code> -optional
> http-status <code> -optional

Optionals:

-s, -short | Short description
-p, -plain | Plain text without colors

Example:

> http-status 200
> http-status l 200
> http-status lookup 200
> http-status 200 

Output:

Found exact match:
200 » OK » "indicates that the request has succeeded."

OR

Found multiple matches:
400 » Bad Request » "indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process."
401 » Unauthorized » "indicates that the request has not been applied because it lacks valid authentication credentials for the target resource."
402 » Payment Required » *reserved*
403 » Forbidden » "indicates that the server understood the request but refuses to authorize it."
404 » Not Found » "indicates that the origin server did not find a current representation for the target resource or is not willing to disclose that one exists."
405 » Method Not Allowed » "indicates that the method specified in the request-line is known by the origin server but not supported by the target resource."
406 » Not Acceptable » "indicates that the target resource does not have a current representation that would be acceptable to the user agent, according to the proactive negotiation header fields received in the request, and the serv
er is unwilling to supply a default representation."
407 » Proxy Authentication Required » "is similar to 401 (Unauthorized), but indicates that the client needs to authenticate itself in order to use a proxy."
408 » Request Timeout » "indicates that the server did not receive a complete request message within the time that it was prepared to wait."
409 » Conflict » "indicates that the request could not be completed due to a conflict with the current state of the resource."
410 » Gone » "indicates that access to the target resource is no longer available at the origin server and that this condition is likely to be permanent."
411 » Length Required » "indicates that the server refuses to accept the request without a defined Content-Length."
412 » Precondition Failed » "indicates that one or more preconditions given in the request header fields evaluated to false when tested on the server."
413 » Payload Too Large » "indicates that the server is refusing to process a request because the request payload is larger than the server is willing or able to process."
414 » URI Too Long » "indicates that the server is refusing to service the request because the request-target is longer than the server is willing to interpret."
415 » Unsupported Media Type » "indicates that the origin server is refusing to service the request because the payload is in a format not supported by the target resource for this method."
an excessive request of small or overlapping ranges."
418 » I'm a teapot » "Any attempt to brew coffee with a teapot should result in the error code 418 I'm a teapot."
Found exact match:
400 » Bad Request » "indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process."