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

@readme/eslint-config

v14.0.0

Published

ReadMe coding standards

Downloads

11,235

Readme

@readme/eslint-config

Core coding standards for ReadMe projects.

npm Build

Installation

You'll need to install ESLint and Prettier into your project. Use this shortcut to install them alongside the config (if using npm 5+):

npx install-peerdeps --dev @readme/eslint-config

If you already have eslint and prettier installed in your project you run this command to install the config:

npm install --save-dev @readme/eslint-config

Usage

Create a .eslintrc file with the following contents:

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

Configs

| Config | Description | | :-- | :--- | | @readme/eslint-config | Rules for a pure JS codebase. |

Specialties

Note If you use one, or both of these, you should also extend @readme/eslint-config.

| Config | Description | | :-- | :--- | | @readme/eslint-config/esm | Rules for ESM codebases. | | @readme/eslint-config/react | Rules for codebases that use React. | | @readme/eslint-config/typescript | Rules for a TS codebase. |

Unit testing

| Config | Description | | :-- | :--- | | @readme/eslint-config/testing/jest | Rules specific to the Jest test runner. | | @readme/eslint-config/testing/jest-dom | Jest-specific rules for when testing, and using jest-dom. Automaticaly imports @readme/eslint-config/testing/jest. | |@readme/eslint-config/testing/react | Rules specific to React codebases where you use @testing-library/react. Is specific to neither Jest or Vitest. | @readme/eslint-config/testing/vitest | Rules specific to the Vitest test runner.

Prettier

Included in this is our shared Prettier config. You can use it in your application by adding the following to your package.json:

"prettier": "@readme/eslint-config/prettier"