babel/eslint/babel-eslint-plugin-development
Kai Cataldo 4ac9c7afe2
Upgrade to ESLint v7 (#11857)
* Upgrade to ESLint v7

* Upgrade eslint-plugin-import

* Update peer deps

* Remove max-len from ESLint config

* Update tests

* Only test babel-eslint-* packages in Node >=10

* Remove babel-eslint

* Fix linking in dev

* Add comment to Makefile

* Fix e2e tests

* Add --ignore-engines flag when installing in ESLint packages

* fix: convert tt.questionDot to Punctuator

* chore: update lockfile

Co-authored-by: Huáng Jùnliàng <jlhwung@gmail.com>
2020-07-29 19:11:48 -04:00
..
2020-07-16 16:01:20 -05:00
2020-07-29 19:11:48 -04:00
2020-07-29 19:11:48 -04:00
Typo 🤦
2018-12-18 22:33:27 +01:00
2020-07-29 19:11:48 -04:00

@babel/eslint-plugin-development

A set of eslint rules to enforce best practices in the development of Babel plugins.

Installation

You'll first need to install ESLint:

$ npm install --save-dev eslint

Next, install @babel/eslint-plugin-development:

$ npm install --save-dev @babel/eslint-plugin-development

Then, load the plugin in your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

{
  "plugins": ["@babel/development"]
}

Supported Rules

Note: Rules marked with 🔧 are autofixable.

  • @babel/development/no-deprecated-clone (🔧): Disallows using the deprecated t.clone(node) and t.cloneDeep(node) methods from @babel/types. Those calls are replaced with t.cloneNode(node) when using eslint --fix.
  • @babel/development/no-undefined-identifier: Disallows using t.identifier("undefined") to create a node which represents an undefined value, since it might cause problem if undefined is redeclared.
  • @babel/development/plugin-name: Requires plugins to have a name property, which can be useful for debugging purposes.