We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[email protected]
@typescript-eslint/[email protected]
Judging by this part of the README I assume that eslint-plugin-mdx should work with the @typescript-eslint/parser.
eslint-plugin-mdx
@typescript-eslint/parser
I use the following versions of the libraries:
eslint
eslint-plugin-react
Definition for rule 'react/jsx-no-undef' was not found
With this config:
module.exports = { parser: "@typescript-eslint/parser", extends: ["plugin:react/recommended", "plugin:mdx/recommended"], settings: { react: { version: "detect", }, }, };
Then I run console command for one file:
yarn eslint 'path-to-file.mdx'
I'm getting this error in the CLI:
1:2 error Parsing error: Expression expected
But then I remove parser: "@typescript-eslint/parser", from the config it works as expected.
parser: "@typescript-eslint/parser",
The text was updated successfully, but these errors were encountered:
#251 (comment)
Sorry, something went wrong.
By the way, PR welcome to improve the document.
Understood, thank you!
No branches or pull requests
Judging by this part of the README I assume that
eslint-plugin-mdx
should work with the@typescript-eslint/parser
.I use the following versions of the libraries:
@typescript-eslint/parser
– 4.15.2.eslint
– 7.21.0.eslint-plugin-mdx
– 1.9.0.eslint-plugin-react
– 7.22.0. (Without this plugin I'm getting errorDefinition for rule 'react/jsx-no-undef' was not found
).With this config:
Then I run console command for one file:
I'm getting this error in the CLI:
But then I remove
parser: "@typescript-eslint/parser",
from the config it works as expected.The text was updated successfully, but these errors were encountered: