npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

yarn-or-die

v1.1.0

Published

Force using yarn instead of npm

Downloads

7

Readme

yarn-or-die

Force using yarn instead of npm in package.json scripts.

Installing

Install as a dev dependency.

npm install --save-dev yarn-or-die

Or using yarn

yarn add -D yarn-or-die

Using

In package.json, add a pre-script that ensures yarn is being used. Example:

  "scripts": {
    "pretest": "yarn-or-die",
    "test": "echo hello"
  }

If you want to ensure yarn is being used to install packages, you can do like this:

  "scripts": {
    "preinstall": "yarn-or-die"
  }

If you now issue the command npm install, an exception will be thrown and install will not run. If you run yarn or yarn install, the installation will continue. This can be useful if you depend on all developers in your team using the yarn.lock file.

Use yarn --ignore-scripts or npm install --ignore-scripts if you run into trouble the first time you run yarn, yarn install or npm install because yarn-or-die is not installed