Package Exports
- validate.io-buffer
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (validate.io-buffer) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
buffer
Validates if a value is a Buffer object.
Installation
$ npm install validate.io-bufferUsage
var isBuffer = require( 'validate.io-buffer' );isBuffer( value )
Validates if a value is a Buffer object.
var value = new Buffer( [1,2,3,4] );
var bool = isBuffer( value );
// returns trueNotes
Validates both [Node.js][node-buffer] and [browser][browser-buffer] (polyfill) `Buffer` objects.
Examples
var isBuffer = require( 'validate.io-buffer' );
console.log( isBuffer( new Buffer( [1,2,3,4] ) ) );
// returns true
console.log( isBuffer( new Buffer( 'beep' ) ) );
// returns true
console.log( isBuffer( [] ) );
// returns falseTo run the example code from the top-level application directory,
$ node ./examples/index.jsTests
Unit
This repository uses tape for unit tests. To run the tests, execute the following command in the top-level application directory:
$ make testAll new feature development should have corresponding unit tests to validate correct functionality.
Test Coverage
This repository uses Istanbul as its code coverage tool. To generate a test coverage report, execute the following command in the top-level application directory:
$ make test-covIstanbul creates a ./reports/coverage directory. To access an HTML version of the report,
$ make view-covBrowser Support
This repository uses Testling for browser testing. To run the tests in a (headless) local web browser, execute the following command in the top-level application directory:
$ make test-browsersTo view the tests in a local web browser,
$ make view-browser-testsLicense
Copyright
Copyright © 2015. Athan Reines.