If command yarn
exists it uses Yarn to install, otherwise fallbacks to npm.
$ npm install --save yarn-install
const install = require('yarn-install')
const result = install(['webpack', 'mocha'])
//=> result, returned by child_process.spawnSync
yarn global add yarn-install
# then you will have `yarn-install` & `yarn-remove` commands
yarn-install pokemon --dev
yarn-install yo --global
yarn-remove xo
# don't forget that `yarn-install` with dependencies is always `--save` by default.
yarn-install help
yarn-remove help
Type: array
An array of dependencies to install, you can omit it to install dependencies in package.json
. If dependencies
is present, it defaults to --save
mode.
install(['ava', 'koa'], options)
// or
install(options)
Type: string
The directory to run the command.
Type: string
Specfic a custom npm registry to use.
Type: boolean
Use --dev
for Yarn and --save-dev
for npm.
Type: boolean
Install globally, stands for npm --global
or yarn global
.
Type: boolean
Default: false
The reversed behavior to install
, ie. yarn remove
and npm uninstall
- Fork it!
- Create your feature branch:
git checkout -b my-new-feature
- Commit your changes:
git commit -am 'Add some feature'
- Push to the branch:
git push origin my-new-feature
- Submit a pull request :D