1. Background
The project was started with the following error:
error Parsing error: Unexpected token <
II. Solution
2.1 installation of Babel eslint
yarn add babel-eslint2.2. eslintrc.JS configuration
"parser": "babel-eslint",2.3. Start the project again and the problem disappears
3. Welcome to exchange and correct.
Read More:
- Parsing error in eslint parsing: unexpected token [How to Solve]
- vue VM682:1 Uncaught SyntaxError: Unexpected token u in JSON at position 0
- Refresh 404 after packaging Vue project, uncaught syntax error: unexpected token ＜
- R: Data frame index error “unexpected token”
- How to Solve Error: “syntax error near unexpected token `newline’”
- Eslint error “no undef” and eslint rule configuration in Vue cli3
- [Solved] Parsing JSON error unexpected end of JSON input
- Webpack Pack and compress ES6 files with errors: ERROR in js/xxxxxx.js from UglifyJs Unexpected token punc ()
- [Soled] Eslint Error: Unexpected literal in error position of callback
- Template cannot be rendered due to the joint query of populate in mongoose: syntax error: unexpected token r in JSON at position 0
- Error reported with decorator in vue: Parsing error: Decorators cannot be used to decorate object literal properties
- Vscode configures eslint to solve terminal syntax error
- Tomcat Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors
- Turn off eslint checksum and resolve formatting conflicts
- Eslint Error:“Identifier xxx is not in camel case“
- [Solved] error [email protected]: The engine “node” is incompatible with this module.
- [Solved] Parsing error: The keyword ‘import‘ is reserved
- [How to Solve] Unexpected space before function parentheses Error
- Solution of “TCLs parsing failed” when dnf starts
- [Solved] Vue3 Eslint Error: The template root requires exactly one element