@babel/eslint-parser - npm Package Compare versions

Comparing version 7.12.1 to 7.12.13

package.json

		{
		"name": "@babel/eslint-parser",
		"version": "7.12.1",
		"version": "7.12.13",
		"description": "ESLint parser that allows for linting of experimental syntax transformed by Babel",
		"author": "The Babel Team (https://babeljs.io/team)",
		"author": "The Babel Team (https://babel.dev/team)",
		"license": "MIT",
		@@ -18,3 +18,3 @@ "repository": {
		},
		"homepage": "https://babeljs.io/",
		"homepage": "https://babel.dev/",
		"engines": {
		@@ -39,7 +39,6 @@ "node": "^10.13.0 \|\| ^12.13.0 \|\| >=14.0.0"
		"devDependencies": {
		"@babel/core": "^7.12.1",
		"@babel/core": "7.12.13",
		"dedent": "^0.7.0",
		"eslint": "^7.5.0",
		"lodash.clonedeep": "^4.5.0"
		"eslint": "^7.5.0"
		}
		}

README.md

		@@ -10,3 +10,3 @@ # @babel/eslint-parser [![npm](https://img.shields.io/npm/v/@babel/eslint-parser.svg)](https://www.npmjs.com/package/@babel/eslint-parser) [![travis](https://img.shields.io/travis/babel/@babel/eslint-parser/main.svg)](https://travis-ci.org/babel/@babel/eslint-parser) [![npm-downloads](https://img.shields.io/npm/dm/@babel/eslint-parser.svg)](https://www.npmjs.com/package/@babel/eslint-parser)

		Note: You only need to use @babel/parser-eslint if you are using Babel to transform your code. If this is not the case, please use the relevant parser for your chosen flavor of ECMAScript (note that the default parser supports all non-experimental syntax as well as JSX).
		Note: You only need to use @babel/eslint-parser if you are using Babel to transform your code. If this is not the case, please use the relevant parser for your chosen flavor of ECMAScript (note that the default parser supports all non-experimental syntax as well as JSX).

		@@ -101,22 +101,6 @@ ## How does it work?

		## Known issues
		## TypeScript

		Flow:
		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.

		> Check out [eslint-plugin-flowtype](https://github.com/gajus/eslint-plugin-flowtype): An `eslint` plugin that makes flow type annotations global variables and marks declarations as used. Solves the problem of false positives with `no-undef` and `no-unused-vars`.

		- `no-undef` for global flow types: `ReactElement`, `ReactClass` [#130](https://github.com/babel/@babel/eslint-parser/issues/130#issuecomment-111215076)
		- Workaround: define types as globals in `.eslintrc` or define types and import them `import type ReactElement from './types'`
		- `no-unused-vars/no-undef` with Flow declarations (`declare module A {}`) [#132](https://github.com/babel/@babel/eslint-parser/issues/132#issuecomment-112815926)

		Modules/strict mode

		- `no-unused-vars: ["error", { vars: local }]` [#136](https://github.com/babel/@babel/eslint-parser/issues/136)

		Please check out [eslint-plugin-react](https://github.com/yannickcr/eslint-plugin-react) for React/JSX issues.

		- `no-unused-vars` with jsx

		Please check out [eslint-plugin-babel](https://github.com/babel/eslint-plugin-babel) for other issues.

		## Questions and support
		@@ -123,0 +107,0 @@

@babel/eslint-parser - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Worsened metrics