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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@quave/eslint-config-quave

v3.0.1

Published

ESLint configurations used by Quave for JavaScript projects

Downloads

1,844

Readme

@quave/eslint-config-quave

npm version

@quave/eslint-config-quave is a group of eslint and prettier configurations to make your Meteor application organized in a standard way.

Why

We believe applications should be organized and checked before every commit.

We believe we are not reinventing the wheel in this package but what we are doing is like putting together the wheels in the vehicle :).

Installation

Install the npm dependency

npm i -D @quave/eslint-config-quave

Add to the root of your package.json

  "eslintConfig": {
    "extends": [
      "@quave/quave"
    ]
  },

Create in the root of your project prettier.config.js file and paste this

module.exports = require('@quave/eslint-config-quave/prettier.config');

Create in the root of your project .prettierignore file and paste this

.meteor

Script examples

Set the custom commands if you want to run eslint or prettier manually or both. Add this to your package.json

  {
    "scripts": {
      "quave-eslint": "eslint . --fix",
      "quave-prettier": "prettier --write \"**/*.js\"",
      "quave-check": "npm run quave-eslint && npm run quave-prettier"
    }
  }

If you have jsx files as well, you can use:

  "quave-prettier": "prettier --write \"**/*.js\" \"**/*.jsx\"",

Automatic check before commit

Automatic check your changed files before every commit.

Install lefthook:

npm i -D lefthook

then create a file called lefthook.yml in the root of your project and paste this:

pre-commit:
  commands:
    quave-check:
      run: npm run quave-check
    update-index:
      run: git update-index --again

In the past we used husky but lefthook is much better in terms of dependency and speed.

Limitations

We consider an error console.log but in some cases you want to use it, then you should disable for the next line and use it.

// eslint-disable-next-line no-console
console.log('Important log...');

License

MIT