GitXplorerGitXplorer
m

check-pkg-engines

public
3 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
4c6b6c246e3c95a754d040819800acfefa01fd52

0.1.1

mmarcioj committed 9 years ago
Unverified
2f2557372586ce1be3cf01e0e075dc7e4006e835

Remove npm from engines field

mmarcioj committed 9 years ago
Unverified
45dde8b006c877c8bb1819e9a46e738f9996b3e6

0.1.0

mmarcioj committed 9 years ago
Unverified
5a0e34500f096dd71ffa3b611d1c75c15e4288a0

Update README.md

mmarcioj committed 9 years ago
Unverified
ecc6b0c595d7f6f8213c6ca62de5f263b9da3c16

Initial release

mmarcioj committed 9 years ago
Unverified
a573d40dc6c569ee50b302488743afdee3f40784

Initial commit

mmarcioj committed 9 years ago

README

The README file for this repository.

check-pkg-engines

Command line utility to check if your package.json engines field matches with your current installed binaries

Build Status

Installation

npm install check-pkg-engines

Usage

For instance given the following package.json

{
  "engines": {
    "node": "^0.10.0",
    "npm": "^2.0.0"
  }
}

If you have installed node v0.12.9 and npm 3.5.3, running check-pkg-engines will exit with an error code and display the following:

~ check-pkg-engines
Incompatible engines versions, please update them to the requested version especified in package.json engines field
The current npm version is 3.5.3 but package.json engines.npm field needs ^2.0.0
The current node version is v0.12.9 but package.json engines.node field needs ^0.10.0

Running Tests

npm test

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request