akameco / prioritize-yarn

If the project has yarn.lock, change npm install to yarn.

prioritize-yarn

If the project has yarn.lock, change npm install to yarn.

CLI

$ npm install --global prioritize-yarn

$ alias npm='prioritize-yarn'
// Using yarn, when there is a `yarn.lock`.
$ npm install
yarn install v0.18.1
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
✨  Done in 2.25s.

Recommend

Add this to ~/.bashrc or ~/.zshrc:

alias npm=prioritize-yarn

Contributors

Thanks goes to these wonderful people (emoji key):

akameco 💻 📖 🚇

Miguel Madero 💻

This project follows the all-contributors specification. Contributions of any kind welcome!

License

MIT © akameco

prioritize-yarn's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

--save and --save-dev not working

A repo without yarn lock (and hence falling back to npm) file won't add the dependencies to the package.json not even specifying --save or --save-dev

Handle remove as well

version:

• node version: 11.9.0
• npm (or yarn) version: 6.7.0 & 1.13.0

Do you want to request a feature or report a bug?:

Feature

What is the current behavior?:

Doesn't work with uninstalls.

What is the expected behavior?:

Similar to it handling installs with --save and --save-dev, etc. It would be nice if this module also handled uninstalls, because yarn expects remove instead of uninstall and there might be optional flags as well.

Suggested solution:

See above.

Handle npm link as well

Related to #5, npm link and npm link <packagename> should probably also be redirected to yarn link. Otherwise npm installs all deps and creates a lockfile before linking.

version:

• node version: 11.9.0
• npm (or yarn) version: 6.7.0 & 1.13.0

Do you want to request a feature or report a bug?:

Feature

What is the current behavior?:

Doesn't work with link.

What is the expected behavior?:

Similar to it handling installs with --save and --save-dev, etc. It would be nice if this module also handled link.

Suggested solution:

See above.