JSPM – is-missing@0.0.1

Package Exports

is-missing

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 (is-missing) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Check that given name exists in npm registry or github as user`s repository.

Install

npm i --save is-missing
npm test
is-missing --help

Usage

For more use-cases see the tests

var isMissing = require('is-missing');

isMissing('some-no-existing-npm-package-name', function _cb(err, bool) {
  console.log(bool);
  //=> false
});

isMissing('mochajs/mocha', function _cb(err, bool) {
  console.log(bool);
  //=> true
});

isMissing('mochajs/not-existing-repository', function _cb(err, bool) {
  console.log(bool);
  //=> false
});

CLI

run is-missing --help or try this one

npm i -g is-missing

is-missing not-existing-npm-package-name

  Aloha, master! How r u today?

  ✔ Oh yes, not-existing-npm-package-name will be yours.

Author

Charlike Mike Reagent

License

Proudly generated by docks(1), April 1, 2015