{ "name": "clite", "description": "A slight CLI framework", "main": "./index.js", "scripts": { "lint": "jscs lib/*.js -v", "check-only": "! grep 'test.only' test/**/*.test.js -n", "tap": "tap test/**/*.test.js --cov", "test": "npm run check-only && npm run lint && npm run tap", "cover": "tap test/**/*.test.js --cov --coverage-report=lcov && npm run check-only", "build": "babel lib --out-dir dist", "semantic-release": "semantic-release pre && npm publish && semantic-release post" }, "bin": { "clite": "cli/index.js" }, "config": { "validate-commit-msg": { "helpMessage": "\n-----------\n\nThere was a small validation problem with your commit message:\n\n> %s\n\nIt's not a huge problem, but a valid commit message will ensure\nwhether your commit triggers a release or not (and sometimes the\ncommit won't need to trigger a release). If you really need to, you\ncan skip the validation using `git commit --no-verify`.\n\nIf your commit is a fix, it might want to be:\n\n> fix: storage bug\n\nOr a feature:\n\n> feat: added new storage process\n\nThere's also `docs`, `test` and `chore` and a few more. To read\nhow the commit message should be formatted, please see this short\npost: https://git.io/v2Nnm\n" }, "ghooks": { "commit-msg": "validate-commit-msg", "pre-push": "npm test" } }, "keywords": [ "cli", "terminal", "framework" ], "author": "Remy Sharp", "license": "MIT", "devDependencies": { "babel-cli": "^6.5.1", "babel-preset-es2015": "^6.5.0", "ghooks": "^1.0.3", "jscs": "^2.10.1", "mock-stdin": "^0.3.0", "proxyquire": "^1.7.4", "rimraf": "^2.5.2", "semantic-release": "^4.3.5", "tap": "^5.4.3", "tap-only": "0.0.5", "validate-commit-msg": "^2.3.0" }, "dependencies": { "abbrev": "^1.0.7", "debug": "^2.2.0", "es6-promise": "^3.1.2", "lodash.defaults": "^4.0.1", "lodash.defaultsdeep": "^4.3.1", "lodash.mergewith": "^4.3.1", "then-fs": "^2.0.0", "update-notifier": "^0.6.0", "yargs": "^4.3.2" }, "repository": { "type": "git", "url": "https://github.com/remy/clite.git" } }