ESLint rules that enforce best practices in the development of Babel plugins.
Last updated 4 months ago by jlhwung .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install @babel/eslint-plugin-development 
SYNC missed versions from official npm registry.


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


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 :wrench: are autofixable.

  • @babel/development/no-deprecated-clone (:wrench:): 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.

Current Tags

  • 7.11.0                                ...           latest (4 months ago)

2 Versions

  • 7.11.0                                ...           4 months ago
  • 1.0.1                                ...           2 years ago
Today 0
This Week 0
This Month 5
Last Day 0
Last Week 0
Last Month 20
Dependencies (0)
Dev Dependencies (1)
Dependents (0)

Copyright 2014 - 2016 © taobao.org |