-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
JSX not allowed in files with extension '' (react/jsx-filename-extension) #1348
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
Comments
What happens on the command line? Editors often have linter bugs that are in fact a bug in the editor, so it's important to eliminate that variable from the equation. |
Hey @ljharb, thanks so much for the speedy reply. :) CLI exits cleanly, however I do see some warnings thrown from eslint when running with
however, based on your input from this thread, it seems like these particular warnings aren't a problem. Here's the output from the Sublime Text console while running the linter internally:
|
Seems from the stack trace that the linter is passing the filename to stdin code, and that might have a bug. Can you reproduce the failure on the command line from stdin? |
Turns out it was an extension config error in my editor. No problem with eslint or the plugin. Apologies! |
@tconroy I'm having the same issue. What did you do to fix it? |
@drew-wallace There's is a good fix on Stackoverflow
|
Remove ESLint extension from your Vs Code. |
Hey there -
For some unknown reason, I'm getting the following error on a
.jsx
component file:The plugin seems to believe my file has no extension(
''
)? Not exactly sure what could be the cause of this.Running Sublime Text 3 + eslintner package, here's my eslint config:
The text was updated successfully, but these errors were encountered: