JSPM – is-missing@1.0.2

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 or user/repo exists in npm registry or in github as organization/user repository.

Install

npm i is-missing --save
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 is-missing -g

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

  Aloha, master! How r u today?

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

abbrev-kindof: kind-of with single letter abbreviations to javascript native types, like kindof(val, 'soa') will return true… more
detect-installed: Checks that given package name is installed locally (in current working directory) or globally.
is-installed: Checks that given package is installed on the system - globally or locally.
jstransformer: Normalize the API of any jstransformer
npm-pkgs: List user npm packages from the npmjs.com!
online-branch-exist: Check that given branch/tag/release exist in github repo, using user/repo#branch pattern.

Author

Charlike Mike Reagent

License

Proudly generated by docks(1), May 6, 2015

is-missing