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

@infuse/eslint-config

v2.0.4

Published

Eslint rules for the Infuse organization

Downloads

24

Readme

Infuse Eslint Config

Installation

yarn add -D eslint @infuse/eslint-config

Usage

When working on a React project, for example, create .eslintrc.json at the root of your project with the contents:

{ "extends": ["@infuse/eslint-config/react"] }

In your test subdirectory, create another .eslintrc.json with the contents:

{ "extends": ["@infuse/eslint-config/jest"] }

The available configs are:

  • node
  • react
  • react-native
  • jest
  • mocha
  • typescript

Peer Dependencies

Dependencies of ESLint configs are listed in package.json under peerDependencies. For some background, see:

  • https://github.com/eslint/eslint/issues/2518
  • https://github.com/eslint/rfcs/pull/5

The peer dependencies listed in this project's package.json are the minimum required to make all of the configs work. You will only ever need a subset of them, depending on the config you are using.

This project's devDependencies are those required to run the base config, because that config is used to lint the project itself. Because they are required by the base config, it might be helpful to begin by installing those peerDependencies that are also listed as devDependencies, then continue installing peerDependencies as required by any ESLint errors.

Contribution

If you find yourself making an exception to these rules consistently or think that any others should be standardized, please open an issue or submit a PR. Please maintain separation of environments and proper inheritance.

All configs must be kept at the project root for nice imports (@infuse/eslint-config/node, etc).

To generate json specifying all rules being applied to a particular file, run:

npx eslint --print-config <file>