jaebradley / http-status-identifier-cli

🔍 What's my HTTP status...without leaving the command line

HTTP Status Identifier CLI

• Purpose
• Installation
• Usage
  • Examples
    • Get the HTTP Status for HTTP Status Code 200
    • Get the HTTP Status for HTTP Status Name I'm a teapot
    • Get the HTTP Status with additional information
    • Get the HTTP Statuses for HTTP Status Codes 100, 200, 300, 400, and 500
    • Get the HTTP Statuses for a combination of HTTP Status Codes (100, 200) and HTTP Status Names (I'm a teapot, Bad Request)
    • Get the HTTP Status for 200 and open the documentation page in the default browser

Purpose

A command line interface to identify HTTP statuses from status codes (i.e. 200) or status names (i.e. I'm a teapot).

Installation

Install via NPM (the -g flag will install the package globally):

npm install http-status-identifier-cli -g

Usage

The command to identify HTTP statuses is hs.

It expects a list of HTTP status codes or HTTP status names. It will return a table containing the HTTP status names, HTTP status codes, and the meaning of the specified HTTP statuses.

If the -f (or --fullDescription) flag is included, an additional supplementary information field is included that provides even more information into the HTTP status. Sometimes, this field is empty if there is no additional information.

If the -d of (--documentation) flag is included, your default browser will open the documentation pages for each of the specified HTTP statuses.

The -h (or --help) flag is useful if you ever need help.

Examples

Get the HTTP Status for HTTP Status Code 200

hs 200

Get the HTTP Status for HTTP Status Name I'm a teapot

hs "I'm a teapot"

Get the HTTP Status with additional information

hs 200 -f

Get the HTTP Statuses for HTTP Status Codes 100, 200, 300, 400, and 500

hs 100 200 300 400 500

Get the HTTP Statuses for a combination of HTTP Status Codes (100, 200) and HTTP Status Names (I'm a teapot, Bad Request)

hs 100 "I'm a teapot" 200 "Bad request"

Get the HTTP Status for 200 and open the documentation page in the default browser

hs 200 -d

http-status-identifier-cli's Issues

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

• • The devDependency @babel/cli was updated from 7.6.4 to 7.7.0.

• The devDependency @babel/core was updated from 7.6.4 to 7.7.0.
• The devDependency @babel/preset-env was updated from 7.6.3 to 7.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Add formatting

Status should be bolded / underlined (etc).

Command that prints out all statuses

Should just be name - status code

Add cat status support?

https://http.cat/

Handle Errors Better

Command that prints out statuses for a range

• Format should be name - status code
• Should add helper commands for 1xx, 2xx, 3xx, 4xx

Add some emoji fun

Uhhhh obviously I'm a teapot needs a teapot emoji.

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

• • The devDependency @babel/cli was updated from 7.6.4 to 7.7.0.

• The devDependency @babel/core was updated from 7.6.4 to 7.7.0.
• The devDependency @babel/preset-env was updated from 7.7.0 to 7.7.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-import is breaking the build 🚨

The devDependency eslint-plugin-import was updated from 2.16.0 to 2.17.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 61 commits.

• 0499050 bump to v2.17.0
• f479635 [webpack] v0.11.1
• 8a4226d Merge pull request #1320 from bradzacher/export-ts-namespaces
• 988e12b fix(export): Support typescript namespaces
• 70c3679 [docs] make rule names consistent
• 6ab25ea [Tests] skip a TS test in eslint < 4
• 405900e [Tests] fix tests from #1319
• 2098797 [fix] export: false positives for typescript type + value export
• 70a59fe [fix] Fix overwriting of dynamic import() CallExpression
• e4850df [ExportMap] fix condition for checking if block comment
• 918567d [fix] namespace: add check for null ExportMap
• 2d21c4c Merge pull request #1297 from echenley/ech/fix-isBuiltIn-local-aliases
• 0ff1c83 [dev deps] lock typescript to ~, since it doesn’t follow semver
• 40bf40a [*] [deps] update resolve
• 28dd614 Merge pull request #1304 from bradennapier/feature/typescript-export-type

There are 61 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.9.15 to 15.9.16.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v15.9.16

15.9.16 (2018-09-19)

Bug Fixes

• package: update env-ci to version 3.0.0 (b9ae7d2)

Commits

The new version differs by 2 commits.

• b9ae7d2 fix(package): update env-ci to version 3.0.0
• c27e18e chore(package): update nock to version 10.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Allow option to open documentation URL