ESLint + Prettier Config

Overview

This configuration extends airbnb ESLint config, with airbnb/hooks enabled, and Prettier integration via the ESLint plugin. Additionally, a few default rules are overriden 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-jerrywang

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

• eslint
• eslint-config-airbnb
• eslint-config-prettier
• eslint-import-resolver-alias
• eslint-plugin-import
• eslint-plugin-jsx-a11y
• eslint-plugin-prettier
• eslint-plugin-react
• eslint-plugin-react-hooks
• eslint-plugin-simple-import-sort
• prettier
• prettier-plugin-tailwindcss

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

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

Usage

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

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

or the .eslintrc file:

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

Import Alias

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

{
  "import/resolver": {
    "alias": {
      "map": [["@", "./src"]],
      "extensions": [".js", ".jsx"]
    }
  }
}

This will allow you to write imports like this anywhere in your code:

import Foo from "@/components/foo";

instead of relative paths:

import Foo from "../../components/foo";

when using absolute imports and module path aliases in Next.js.

This can also be overriden in your local .eslintrc file, if needed:

// .eslintrc
{
  "extends": ["jerrywang"],
  "settings": {
    "import/resolver": {
      "alias": {
        "map": [["@", "./lib"]],
        "extensions": [".js"]
      }
    }
  }
}

Prettier

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

If you wish to override any Prettier options, you can do so by specifying them under prettier/prettier rule in your ESLint config file. For example:

// .eslintrc
{
  "extends": ["jerrywang"],
  "rules": {
    "prettier/prettier": [
      "error",
      {
        "printWidth": 90
      }
    ]
  }
}

Make sure that these rules match the options specified in your .prettierrc file.

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 ."
  }
}

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": "eslint --ignore-path .gitignore --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.

Credits

All credits to

• Youtube Video
• Github

Deployment with Github Action

• add secret

• Click tag on Github, and create new release, then the action will run.

OR

Steps

• made new changes and commit and push.
• npm run pub will patch new npm version and push new tag.
• at tag page, find the tag you are going to publish and create new release from there.

License

Licensed under MIT License.

• https://choosealicense.com/