babel/eslint/babel-eslint-plugin-development
Nicolò Ribaudo eea156b2cb Migrate from "master" branch to "main" (#11715)
* Remove dead link

* Use consistent "homepage" url in package.json

* Update md links

* Update comment link in parser d.ts

* Add comment in gitpod config

* Update circleci config

* Update PULL_REQUEST_TEMPLATE

* Update badges

* Trigger CI

* Update 404 link
2020-06-18 21:52:29 -04:00
..
Typo 🤦
2018-12-18 22:33:27 +01: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.