The map of HTTP status codes from the builtin http module. Exposes the latest directly from
http
in Node, with a zero-dependencies version for the browser.
$ npm install --save builtin-status-codes
var codes = require('builtin-status-codes')
codes[100]
//=> Continue
To create a new browser build:
$ npm run build
MIT © Ben Drucker
# builtin-status-codes [![Build Status](https://travis-ci.org/bendrucker/builtin-status-codes.svg?branch=master)](https://travis-ci.org/bendrucker/builtin-status-codes) > The map of HTTP status codes from the builtin http module. Exposes the latest directly from `http` in Node, with a zero-dependencies version for the browser. ## Install ``` $ npm install --save builtin-status-codes ``` ## Usage ```js var codes = require('builtin-status-codes') codes[100] //=> Continue ``` ## Build To create a new browser build: ```sh $ npm run build ``` ## License MIT © [Ben Drucker](http://bendrucker.me)
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 19553 | swellard | Move and rename clients | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1.0/javascript/node_modules/builtin-status-codes/readme.md | |||||
#1 | 18810 | tjuricek |
First-pass at JavaScript client SDK. JavaScript requires Node with Gulp to "browserfy" the library. It's the easiest way I found to use the swagger-js project; bundle up a wrapping method. There is no JavaScript reference guide. The swagger-js doesn't really document what they do very well, actually. Overall I'm not particularly impressed by swagger-js, it was hard to even figure out what the right method syntax was. We may want to invest time in doing it better. This required setting CORS response headers, which are currently defaulted to a fairly insecure setting. |