Linux v69820.1blu.de 4.15.0 #1 SMP Mon Sep 30 15:36:27 MSK 2024 x86_64
Apache/2.4.58
Server IP : 195.90.215.149 & Your IP : 216.73.216.250
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
node-babel-eslint-plugin /
Delete
Unzip
Name
Size
Permission
Date
Action
README.md
1.96
KB
-rw-r--r--
2024-02-26 08:46
copyright
13.05
KB
-rw-r--r--
2023-05-30 08:16
Save
Rename
# @babel/eslint-plugin Companion rules for `@babel/eslint-parser`. `@babel/eslint-parser` does a great job at adapting `eslint` for use with Babel, but it can't change the built-in rules to support experimental features. `@babel/eslint-plugin` re-implements problematic rules so they do not give false positives or negatives. > Requires Node 10.13 or greater ### Install ```sh npm install @babel/eslint-plugin --save-dev ``` Load the plugin in your `.eslintrc.json` file: ```json { "plugins": ["@babel"] } ``` Finally enable all the rules you would like to use (remember to disable the original ones as well!). ```json { "rules": { "@babel/new-cap": "error", "@babel/no-invalid-this": "error", "@babel/no-unused-expressions": "error", "@babel/object-curly-spacing": "error", "@babel/semi": "error" } } ``` ### Rules Each rule corresponds to a core `eslint` rule and has the same options. 🛠: means it's autofixable with `--fix`. - `@babel/new-cap`: handles decorators (`@Decorator`) - `@babel/no-invalid-this`: handles class fields and private class methods (`class A { a = this.b; }`) - `@babel/no-unused-expressions`: handles `do` expressions - `@babel/object-curly-spacing`: handles `export * as x from "mod";` (🛠) - `@babel/semi`: Handles class properties (🛠) ## TypeScript While [`@babel/eslint-parser`](https://github.com/babel/babel/tree/main/eslint/babel-eslint-parser) can parse TypeScript, we don't currently support linting TypeScript using the rules in [`@babel/eslint-plugin`](https://github.com/babel/babel/tree/main/eslint/babel-eslint-plugin). This is because the TypeScript community has centered around [`@typescript-eslint`](https://github.com/typescript-eslint/typescript-eslint) and we want to avoid duplicate work. Additionally, since [`@typescript-eslint`](https://github.com/typescript-eslint/typescript-eslint) uses TypeScript under the hood, its rules can be made type-aware, which is something Babel doesn't have the ability to do.