Strip UTF-8 byte order mark (BOM) from a string/buffer
From Wikipedia:
The Unicode Standard permits the BOM in UTF-8, but does not require nor recommend its use. Byte order has no meaning in UTF-8.
$ npm install --save strip-bom
var fs = require('fs');
var stripBom = require('strip-bom');
stripBom('\uFEFFunicorn');
//=> 'unicorn'
stripBom(fs.readFileSync('unicorn.txt'));
//=> 'unicorn'
MIT © Sindre Sorhus
# strip-bom [![Build Status](https://travis-ci.org/sindresorhus/strip-bom.svg?branch=master)](https://travis-ci.org/sindresorhus/strip-bom) > Strip UTF-8 [byte order mark](http://en.wikipedia.org/wiki/Byte_order_mark#UTF-8) (BOM) from a string/buffer From Wikipedia: > The Unicode Standard permits the BOM in UTF-8, but does not require nor recommend its use. Byte order has no meaning in UTF-8. ## Install ``` $ npm install --save strip-bom ``` ## Usage ```js var fs = require('fs'); var stripBom = require('strip-bom'); stripBom('\uFEFFunicorn'); //=> 'unicorn' stripBom(fs.readFileSync('unicorn.txt')); //=> 'unicorn' ``` ## Related - [strip-bom-cli](https://github.com/sindresorhus/strip-bom-cli) - CLI for this module - [strip-bom-stream](https://github.com/sindresorhus/strip-bom-stream) - Stream version of this module ## License MIT © [Sindre Sorhus](http://sindresorhus.com)
# | 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/strip-bom/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. |