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

@repay/eslint-config

v5.1.0

Published

eslint configuration from REPAY

Downloads

50

Readme

@repay/eslint-config

The eslint-config used at REPAY.

Usage

To use this configuration you will need to follow three steps:

  1. install this package via your package manager of choice yarn add -D @repay/eslint-config eslint
  2. install the peer dependencies and configurations yarn repay-eslint install
  3. Ensure that your project has a Babel config file so that the included parser knows how to interpret your code.

To run the linter you should add a "script" to the root package.json such as:

{
  "scripts": {
    "lint": "eslint \"**/*.{js,jsx}\"",
    "fmt": "yarn lint --fix"
  }
}

You will then be able to run the linter using the command: yarn lint. Adding the --fix argument will auto fix any issues which can be listed as yarn fmt above.

Configuring .eslintrc

You may want to extend from @repay/eslint-config in your project's .eslintrc file so that you can make project-specific adjustments.

JS Project

// .eslintrc
{
  "extends": ["@repay/eslint-config"],
  "overrides": [{
    // override any linting rules here
  }]
}

TS Project

// .eslintrc
{
  "extends": ["@repay/eslint-config/ts"],
  "overrides": [{
    // override any linting rules here
  }]
}

If you are configuring this eslint in a TypeScript project, we recommend that you follow the typescript-eslint guidelines for linting with type information found here.

Design Principles

The following priciples should be considered when adding rules.

  • Stylistic options are limited to those exposed by Prettier to reduce bike-shedding
  • Rules should be added with specific purpose in mind to avoid bloat
  • Rules should be either "error" or "off" save for the following two exceptions:
    • very complex rules which are not always accurate
    • new rules that are added in a patch, which will be an error in the next minor version.