-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
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
Incompatibility with @typescript-eslint #92
Comments
Please provide more detail. Including your eslint config, or a minimal runnable reproduction. (This seems a usage question, instead of bug, IMO) You can always use |
Don't enable |
I was also experiencing this issue, I solved it by doing the following:
{
"files": ["*.tsx"],
"extends": ["plugin:@typescript-eslint/recommended-requiring-type-checking"]
} The error went away and linting works fine! |
Could you share your full eslintrc setup? When I use your solution I get the same eslint error in all of my mdx files: |
@jackkrone You'd better provide your reproduction instead. |
@JounQin Sure. I just figured it out, as indicated in #251 (comment) This is what my
I've found that this is required if using the |
When we use the config
@typescript-eslint/recommended-requiring-type-checking
from typescript-eslint we have to setparserOptions.project
.It seems that
eslint-mdx
overwrites theparserOptions.project
config because when we runeslint
we get this error:The text was updated successfully, but these errors were encountered: