Comparing version 1.0.0 to 1.0.1
@@ -5,2 +5,14 @@ # Change Log | ||
<a name="1.0.1"></a> | ||
## [1.0.1](https://github.com/zkat/npx/compare/v1.0.0...v1.0.1) (2017-05-30) | ||
### Bug Fixes | ||
* **build:** add dummy test file to let things build ([6199eb6](https://github.com/zkat/npx/commit/6199eb6)) | ||
* **docs:** fix arg documentation in readme/manpage ([d1cf44c](https://github.com/zkat/npx/commit/d1cf44c)) | ||
* **opts:** add --version/-v ([2633a0e](https://github.com/zkat/npx/commit/2633a0e)) | ||
<a name="1.0.0"></a> | ||
@@ -7,0 +19,0 @@ # 1.0.0 (2017-05-30) |
{ | ||
"name": "npx", | ||
"version": "1.0.0", | ||
"version": "1.0.1", | ||
"description": "execute npm package binaries", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
@@ -65,2 +65,4 @@ 'use strict' | ||
}) | ||
.version() | ||
.alias('version', 'v') | ||
@@ -67,0 +69,0 @@ const opts = parser.getOptions() |
@@ -7,3 +7,3 @@ [![npm](https://img.shields.io/npm/v/npx.svg)](https://npm.im/npx) [![license](https://img.shields.io/npm/l/npx.svg)](https://npm.im/npx) [![Travis](https://img.shields.io/travis/zkat/npx.svg)](https://travis-ci.org/zkat/npx) [![AppVeyor](https://ci.appveyor.com/api/projects/status/github/zkat/npx?svg=true)](https://ci.appveyor.com/project/zkat/npx) [![Coverage Status](https://coveralls.io/repos/github/zkat/npx/badge.svg?branch=latest)](https://coveralls.io/github/zkat/npx?branch=latest) | ||
`npx [--package|-p <package>] [--cache <path>] [--install-dev|-D] [--install-prod|-P] [--userconfig <path>] [-c <string>] <command>[@version] -- [command-arg]...` | ||
`npx [--package|-p <package>] [--cache <path>] [--save-dev|-D] [--save-prod|-P] [--save-optional|-O] [--save-bundle|-B] [--save-exact|-E] [--global|-g] [--prefix|-C] [--userconfig <path>] [-c <string>] [--version|-v] <command>[@version] -- [command-arg]...` | ||
@@ -34,2 +34,4 @@ ## INSTALL | ||
* `-v, --version` - Show the current npx version. | ||
## EXAMPLES | ||
@@ -36,0 +38,0 @@ |
Sorry, the diff of this file is not supported yet
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
16993
266
82
1