Bug: false positive "ESLint: Parsing error: Unexpected token <"
See original GitHub issueEnvironment
Node version: 16.9.1 npm version: 7.23.0 Local ESLint version: Global ESLint version: 8.0.0 beta 2 Operating System: Windows 10 x64 21H1
What parser are you using?
Other
What did you do?
Upgraded to ESLint 8.0.0 beta 2
What did you expect to happen?
No warning at HTML5 page, like it used to be in ESLint 8.0.0 beta 1
<!DOCTYPE html>
<html lang = "en">
What actually happened?
I get «ESLint: Parsing error: Unexpected token <» for
<!DOCTYPE html>
<html lang = "en">
Participation
- I am willing to submit a pull request for this issue.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
ESLint Parsing error: Unexpected token - Stack Overflow
Unexpected token errors in ESLint parsing occur due to incompatibility between your development environment and ESLint's current parsing ...
Read more >ESLint: "Parsing error: Unexpected token" in Visual Studio Code
The solution. Unexpected token errors are caused by incompatibilities in your parser options and the code you're writing. In this case, I'm ...
Read more >PhpStorm 213.4293.18 Release Notes | Knowledge Base
No subsystem Bug WI‑61889
PHP Exception WI‑62990
Bug WI‑62829
Usability WI‑62770
Read more >parsing error: this experimental syntax requires enabling one ...
[Bug]: ESLint: Parsing error: This experimental syntax requires enabling one of the following parser plugin(s): "jsx", "flow", "typescript". #14546.
Read more >@typescript-eslint/eslint-plugin | Yarn - Package Manager
Important: This documentation covers modern versions of Yarn. For 1.x docs, see classic.yarnpkg.com. Yarn.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is likely a problem in the IDE or how it is configured to integrate with ESLint, I don’t see anything in v8.0.0-beta.2 changelog that could possibly change this after upgrading from v8.0.0-beta.1.
Converting to a discussion, as this is an IDE issue and not an ESLint issue.