# httpstatusview

> Displays http status in browser, good for error handling.

Latest version **1.0.2** (published 2020-06-03) · MIT license · 0 weekly downloads

## Install

```sh
npm install httpstatusview
pnpm add httpstatusview
yarn add httpstatusview
bun add httpstatusview
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.2 |
| Published | 2020-06-03 |
| First published | 2020-06-03 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 6.9 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | AFT3RxL1F3 |
| Maintainers | katanadevelopment |
| Keywords | StatusView, NodeJS, ErrorHandleing, HTTP_Status, Http400, Http401, Http500, throwerror, err, error |

## Links

- npm: https://www.npmjs.com/package/httpstatusview
- Repository: https://github.com/FullStackUbuntu/statusview
- Homepage: https://github.com/FullStackUbuntu/statusview#readme
- Issues: https://github.com/FullStackUbuntu/statusview/issues
- npm.io page: https://npm.io/package/httpstatusview

## Alternatives

- [@sentry/react-native](https://npm.io/package/@sentry/react-native.md) — 2.6M weekly downloads
- [@ardatan/aggregate-error](https://npm.io/package/@ardatan/aggregate-error.md) — 708.1K weekly downloads
- [custom-error-generator](https://npm.io/package/custom-error-generator.md) — 2.0K weekly downloads
- [@technik-sde/prosemirror-recreate-transform](https://npm.io/package/@technik-sde/prosemirror-recreate-transform.md) — 1.5K weekly downloads
- [@suchipi/error-utils](https://npm.io/package/@suchipi/error-utils.md) — 78 weekly downloads

## Recent versions

- 1.0.2 (latest) — 2020-06-03
- 1.0.1 — 2020-06-03

## README

CREATED BY: AJ_Chambers-@-KATANA_DEVELOPMENT

HTTP Status Codes Defined:
--------------------------------------------------------------------------------
[400]:  The server cannot or will not process the request due to an apparent 
    client error (e.g., malformed request syntax, size too large, invalid 
    request message framing, or deceptive request routing).

[401]:  Similar to 403 Forbidden, but specifically for use when authentication 
    is required and has failed or has not yet been provided. The response must 
    include a WWW-Authenticate header field containing a challenge applicable to
    the requested resource.

[403]:  The request contained valid data and was understood by the server, but 
    the server is refusing action. This may be due to the user not having the 
    necessary permissions for a resource or needing an account of some sort, or 
    attempting a prohibited action. 

[404]:  The requested resource could not be found but may be available in the 
    future. Subsequent requests by the client are permissible.

[405]:  A request method is not supported for the requested resource; for
    example, a GET request on a form that requires data to be presented via
    POST, or a PUT request on a read-only resource.

[408]:  The server timed out waiting for the request.

[500]:  A generic error message, given when an unexpected condition was
    encountered and no more specific message is suitable.

[501]: The server either does not recognize the request method, or it lacks the
    ability to fulfil the request. Usually this implies future availability (ex.
    a new feature of a web-service API).
--------------------------------------------------------------------------------
!end of 'README.me'!

---
_Source: https://npm.io/package/httpstatusview · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._