-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Parse error in mdx files #1433
Comments
Please try Notice about these new rules: https://github.com/rx-ts/eslint-plugin-mdx#rules |
i have no idea what mdx is, but it’s not JavaScript, or supported by node, or Babel, so you’d definitely need your own eslint parser. |
It would be better to support |
I'm not sure what you mean. That particular utility is for parsing ES Modules or CJS modules (which are files, one module per file) - it's not meant to parse anything else. |
@ljharb Reference: https://eslint.org/docs/developer-guide/working-with-custom-parsers |
Gotcha - in that case, I agree with your suggestion, and a PR would be great. Thanks! |
I updated to |
@cdfa please add a separated issue to |
Hi, I'm reporting here too, because I realized an issue I originally reported at
babel-plugin-module-resolver
might not be specific to that resolver. Please read it for more information.As I commented there, I also get parse errors when using the default node resolver, but on a different import.
import:
Error:
The text was updated successfully, but these errors were encountered: