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

eslint-plugin-esquery

v1.0.0

Published

This ESLint plugin lets users write simple ESLint rules right in their config by leveraging the power of [ESQuery](https://github.com/estools/esquery), which is a CSS-selector-like library for ASTs.

Downloads

9

Readme

eslint-plugin-esquery

This ESLint plugin lets users write simple ESLint rules right in their config by leveraging the power of ESQuery, which is a CSS-selector-like library for ASTs.

Installation

npm install --save-dev eslint-plugin-esquery

Usage

Add "esquery" to your eslint config's "plugins" array, then enable the "eslint/eslint" rule:

{
  "plugins": ["esquery"],
  "rules": {
    "esquery/esquery": "error"
  }
}

This won't do anything unless you specify a config for the rule, though. Give the rule an object where each key is an ESQuery pattern string, and each value is the message to report when that pattern is matched:

{
  "plugins": ["esquery"],
  "rules": {
    "esquery/esquery": ["error", {
      "VariableDeclarator[kind='var']": "Please don't use var.",
      "Identifier[name.length=1]": "Please use a longer identifier name."
    }]
  }
}

If you want a mix of errors and warnings, use the two rules "esquery/esquery-warn" and "esquery/esquery-error" instead:

{
  "plugins": ["esquery"],
  "rules": {
    "esquery/esquery-warn": ["warn", {
      "VariableDeclarator[kind='var']": "Please don't use var."
    }],
    "esquery/esquery-error": ["error", {
      "Identifier[name.length=1]": "Please use a longer identifier name."
    }]
  }
}

If you want the message to be dynamic, use a function that returns a string as the value, instead of a string. You have to use a JS config (.eslintrc.js) instead of a JSON/YAML config to do this.

module.exports = {
  "plugins": ["esquery"],
  "rules": {
    "esquery/esquery": ["error", {
      "Identifier[name.length=1]": (node) =>
        `Please use a longer identifier name, instead of '${node.name}'.`
    }]
  }
}

License

MIT