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-config-acme

v3.1.0

Published

ESLint + Prettier config for React

Downloads

3,586

Readme

ESLint + Prettier Config for React

Shareable config for ESLint and Prettier, aimed primarily to be used in React projects.

Overview

This configuration extends Airbnb ESLint config, with eslint-config-airbnb/hooks enabled, and Prettier integration via the ESLint plugin. Additionally, a few default rules are overridden to provide a more relaxed development experience in Next.js applications out of the box.

The goal of this configuration is to get code linting and formatting up and running as quickly as possible in a modern development environment, without sacrificing cleanliness and readability, and having to configure ESLint + Prettier from scratch every time.

Installation

To install the package, run:

$ npm install -D eslint-config-acme

This will install the shared config, as well as its peer dependencies:

NOTE: if you are on NPM <7, you will need to install these manually:

$ npx install-peerdeps -D eslint-config-acme

Usage

To start using this shared config, add eslint-config-acme (or just acme) to either your package.json:

// package.json
{
  "eslintConfig": {
    "extends": ["acme"]
  }
}

or the .eslintrc configuration file:

// .eslintrc
{
  "extends": ["acme"]
}

NOTE: The new flat config format is not yet supported, as there is an upstream dependency for its support in eslint-config-airbnb.

Import Alias

This config provides a default import alias resolver for eslint-plugin-import to support shorthand imports of local modules:

{
  "import/resolver": {
    "eslint-import-resolver-custom-alias": {
      "alias": {
        "~": "./src",
        "@": "./src",
        "#": "./src",
        "src": "./src"
      },
      "extensions": [".js", ".jsx", ".ts", ".tsx"]
    }
  }
}

This maps any of the above shorthands (~, @, #, src) to the ./src directory in your project, and allows you to write imports like this anywhere in your code:

import Foo from '~/components/Foo';
// or
import Foo from '@/components/Foo';
// or
import Foo from '#/components/Foo';
// or
import Foo from 'src/components/Foo';

instead of relative paths:

import Foo from '../../components/Foo';

Use this alongside absolute imports and module path aliases in Next.js.

These aliases can also be customized in your local configuration file, if needed:

// .eslintrc
{
  "extends": ["acme"],
  "settings": {
    "import/resolver": {
      "eslint-import-resolver-custom-alias": {
        "alias": {
          "lib": "./lib",
          "src": "./some/other/src"
        },
        "extensions": [".js", ".jsx", ".ts", ".tsx", ".mdx"]
      }
    }
  }
}

Import Sorting

Import statement sorting is enabled via @ianvs/prettier-plugin-sort-imports, with the following default importOrder set:

{
  "importOrder": [
    "<TYPES>",
    "<TYPES>^[.]",
    "",
    "<BUILT_IN_MODULES>",
    "",
    "^react$",
    "<THIRD_PARTY_MODULES>",
    "",
    "^(src|~|@|#)(/.*)$",
    "",
    "^[.]"
  ]
}

This will take import statements like these:

import fs from 'node:fs';

import { module } from 'package-name';

import foo from '@/foo';

import main from '../index';
import { bar } from './bar';

And turn them into this:

import fs from 'node:fs';

import { module } from 'package-name';

import foo from '@/foo';

import main from '../index';
import { bar } from './bar';

See the plugin docs for more information on how to customize this option.

Prettier

This config supports Prettier integration out of the box. Rules that may conflict with ESLint are disabled via eslint-config-prettier.

Shared Config

This package provides a shared Prettier config for use alongside ESLint.

To enable, create a Prettier config file (.prettierrc, .prettierrc.js, etc.), and import the shared Prettier config.

JSON:

// .prettierrc
'eslint-config-acme/prettier';

CommonJS:

// .prettierrc.js
/** @type {import("prettier").Config} */
const acme = require('eslint-config-acme/prettier');

module.exports = acme;

If you'd like to override any of the default options, you can use the spread operator (...) to extend the default config:

// .prettierrc.js
/** @type {import("prettier").Config} */
const acme = require('eslint-config-acme/prettier');

const config = {
  ...acme,
  singleQuote: false,
};

module.exports = config;

Adding Scripts

Add the following to your package.json file to define a script that will lint all known files and output the results:

// package.json
{
  "scripts": {
    "lint": "eslint --ignore-path .gitignore ."
  }
}

Or, if using Next.js:

// package.json
{
  "scripts": {
    "lint": "next lint"
  }
}

To fix all automatically-fixable issues, you can add the following script to your package.json as well (in addition to above):

// package.json
{
  "scripts": {
    "lint:fix": "npm run lint -- --fix"
  }
}

Note that you can update the above scripts as you see fit, this is just an example. See ESLint CLI reference for more details.

Author

Mykhaylo Ryechkin

License

MIT