Package Exports

eslint-config-pedant

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (eslint-config-pedant) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

eslint-config-pedant

An ESLint Shareable Config to find errors, typos and potentially dangerous code.

pedant

Install

You'll first need to install ESLint:

$ npm install eslint --save-dev

Note: You may install ESLint globally using the -g flag.

Next, install eslint-config-pedant:

$ npm install eslint-config-pedant --save-dev

Note: If you installed ESLint globally (using the -g flag) then you must also install eslint-config-pedant globally.

A globally-installed instance of ESLint can only use globally-installed ESLint plugins. A locally-installed ESLint can make use of both locally- and globally- installed ESLint plugins.

Usage

Shareable configs are designed to work with the extends feature of .eslintrc files. You can learn more about Shareable Config on the official ESLint website.

Add this to your .eslintrc file:

{
  "extends": "pedant"
}

Note: We omitted the eslint-config- prefix since it is automatically assumed by ESLint.

You can override settings from the shareable config by adding them directly into your .eslintrc file.

FAQ

Whether this config is suitable for me?
Why this config does not contain stylistic rules?

Whether this config is suitable for me?

Most likely this config will suite you, because it contains only those rules which are necessary to find errors, typos and potentially dangerous code.

To make sure that this config is right for you:

Look at the examples of incorrect code.
Look at the rules from this config. The detailed information about each rule you can find on the eslint website.
Try this config in your project. If you agree with those errors then this config is for you.

Why this config does not contain stylistic rules?

This config intentionally does not limit your choice of code style.

If you want to check code style of your my code you can add stylistic rules to your config in your project.

Also, you can create your own Shareable Config or use one of the existing.