The 'statuses' npm package provides an easy way to handle HTTP status codes. It allows you to look up status codes by the code number or by the status message. It also provides a way to retrieve the message associated with a particular status code or vice versa.
Get HTTP status code message
Retrieve the message associated with a specific HTTP status code.
"use strict";
const statuses = require('statuses');
const message = statuses[404]; // 'Not Found'Get HTTP status code by message
Retrieve the status code by specifying the message.
"use strict";
const statuses = require('statuses');
const code = statuses('Not Found'); // 404Check if status code is a redirect
Check if a given status code is classified as a redirect (3xx).
"use strict";
const statuses = require('statuses');
const isRedirect = statuses.redirect[301]; // trueGet the status code range
Determine if a status code falls within a specific range, such as informational (1xx), success (2xx), etc.
"use strict";
const statuses = require('statuses');
const isInformational = statuses.empty[204]; // true
const isSuccess = statuses.success[200]; // trueThis package provides named exports for HTTP status codes and messages, similar to 'statuses'. It allows you to use constants instead of numbers for better readability in your code.
Similar to 'statuses', 'http-status' provides an easy way to reference HTTP status codes and their messages. It also includes utility functions to check the type of status code (e.g., isSuccess, isClientError).
HTTP status utility for node.
This module provides a list of status codes and messages sourced from a few different projects:
This is a Node.js module available through the
npm registry. Installation is done using the
npm install command:
$ npm install statuses
var status = require('statuses')
Returns the status message string for a known HTTP status code. The code may be a number or a string. An error is thrown for an unknown status code.
status(403) // => 'Forbidden'
status('403') // => 'Forbidden'
status(306) // throws
Returns the numeric status code for a known HTTP status message. The message is case-insensitive. An error is thrown for an unknown status message.
status('forbidden') // => 403
status('Forbidden') // => 403
status('foo') // throws
Returns an array of all the status codes as Integers.
Returns the numeric status code for a known status message (in lower-case),
otherwise undefined.
status['not found'] // => 404
Returns true if a status code expects an empty body.
status.empty[200] // => undefined
status.empty[204] // => true
status.empty[304] // => true
Returns the string message for a known numeric status code, otherwise
undefined. This object is the same format as the
Node.js http module http.STATUS_CODES.
status.message[404] // => 'Not Found'
Returns true if a status code is a valid redirect status.
status.redirect[200] // => undefined
status.redirect[301] // => true
Returns true if you should retry the rest.
status.retry[501] // => undefined
status.retry[503] // => true
FAQs
HTTP status utility
The npm package statuses receives a total of 36,424,411 weekly downloads. As such, statuses popularity was classified as popular.
We found that statuses demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.