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-discover

v1.1.0

Published

Quickly discover ESLint plugins for your dependencies

Downloads

8

Readme

eslint-discover

Quickly discover ESLint plugins for your dependencies

Usage

Run npx eslint-discover in your package's root directory. Any known plugins will be discovered if you have the associated package installed (such as eslint-plugin-react for react). You can install discovered plugins as needed. They may include custom rules or shareable configs, so refer to their documentation for full usage instructions.

$ npx eslint-discover
@typescript-eslint/eslint-plugin
eslint-plugin-eslint-plugin
eslint-plugin-jest-dom
eslint-plugin-react
eslint-plugin-react-hooks
eslint-plugin-testing-library

Continuous integration (CI)

It may be useful to automatically check that relevant ESLint plugins are installed as your codebase grows and depends on new technologies. A convenient way to do this is to install eslint-discover in a continuous integration (CI) service like GitHub Actions or Travis CI. The eslint-discover command can be called in CI scripts (or any package.json scripts that your CI service runs). It will return a 1 (failure) exit code if any discovered ESLint plugins are missing, which should fail the build on most CI services.

Limitations

This currently scans dependencies and devDependencies in package.json, so it may miss globally installed packages or dependencies of other packages.