JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 1
  • Score
    100M100P100Q41641F
  • License

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

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

npm standard style build status coverage status deps status

Check that given name or user/repo exists in npm registry or in github as 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.

Author

Charlike Mike Reagent

License MIT license

Copyright (c) 2015 Charlike Mike Reagent, contributors.
Released under the MIT license.


Proudly generated by docks(1) on May 9, 2015.