eslint-plugin-es-roikoren v3.0.0

eslint-plugin-es-roikoren

A re-implementation of eslint-plugin-es in TypeScript.

Disclaimer

First off, I would like to deeply thank @mistycatea and everyone else involved in the original eslint-plugin-es. None of this would have been possible without them, and all credit should go to them.

This package is an attempt to migrate eslint-plugin-es to be written in TypeScript, and to use the great @typescript-eslint repository for plugin development.

Below is taken verbatim from eslint-plugin-es, and will be updated as needed.

🏁 Goal

Espree, the default parser of ESLint, has supported ecmaVersion option. However, the error messages of new syntax are not readable (e.g., "unexpected token" or something like).

When we use this plugin along with the latest ecmaVersion option value, it tells us the readable error message for the new syntax, such as "ES2020 BigInt is forbidden." Plus, this plugin lets us disable each syntactic feature individually.

💿 Installation

Use npm or a compatible tool.

npm install --save-dev eslint eslint-plugin-es-roikoren

yarn add -D eslint eslint-plugin-es-roikoren

IMPORTANT

If you installed eslint globally, you should install this plugin in the same way.

Requirements

• Node.js 12.22.0 or newer.
• ESLint 7.0.0 or newer.

📖 Usage

Configure your .eslintrc.* file.

For example, to enable only Rest/Spread Properties in ES2018, as similar to legacy experimentalObjectRestSpread option:

{
  "plugins": ["es-roikoren"],
  "parserOptions": {
    "ecmaVersion": 2018
  },
  "rules": {
    "es-roikoren/no-async-iteration": "error",
    "es-roikoren/no-malformed-template-literals": "error",
    "es-roikoren/no-regexp-lookbehind-assertions": "error",
    "es-roikoren/no-regexp-named-capture-groups": "error",
    "es-roikoren/no-regexp-s-flag": "error",
    "es-roikoren/no-regexp-unicode-property-escapes": "error"
  }
}

Presets

This plugin provides the following configs.

For example:

{
  "parserOptions": {
    "ecmaVersion": 2021
  },
  "extends": [
    "eslint:recommended",
    "plugin:es-roikoren/restrict-to-es2018"
  ],
  "rules": {
    "es-roikoren/no-rest-spread-properties": "off"
  }
}

The aggressive mode

This plugin never reports prototype methods by default. Because it's hard to know the type of objects, it will cause false positives.

If you configured the aggressive mode, this plugin reports prototype methods even if the rules couldn't know the type of objects. For example:

settings.es.aggressive = true means the aggressive mode.

{
  "plugins": ["es-roikoren"],
  "rules": {
    "es-roikoren/no-string-prototype-codepointat": "error"
  },

  "settings": {
    "es": { "aggressive": true }
  }
}

If using this plugin and TypeScript, this plugin reports prototype methods by default because we can easily know types. For example:

{
  "plugins": ["es-roikoren"],
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "project": "tsconfig.json"
  },
  "rules": {
    "es-roikoren/no-string-prototype-codepointat": "error"
  }
}

If you configured the aggressive mode, this plugin reports prototype methods on any types as well.

{
  "plugins": ["es-roikoren"],
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "project": "tsconfig.json"
  },
  "rules": {
    "es-roikoren/no-string-prototype-codepointat": "error"
  },
  "settings": {
    "es": { "aggressive": true }
  }
}