When using Iview, it reports: https://google.com/#q=vue%2Fno-parsing-error Parsing error: x-invalid-end-tag Solution
Phenomenon

✘  https://google.com/#q=vue%2Fno-parsing-error  Parsing error: x-invalid-end-tag
  src\pages\TheAdminDashboard.vue:11:25
                          </MenuItem>

Solution:

There are two solutions:
1. Modify MenuItem to: menu item 2

2. Add the following in the root directory. Eslintrc.js file rules:

"vue/no-parsing-error": [2, { "x-invalid-end-tag": false }]

Read More:

• Parsing error:x-invalid-end-tag [How to Solve]
• [Solved] Eslint Error: Parsing error: x-invalid-end-tag
• OTS parsing error: invalid version tag [How to Solve]
• [Solved] VUE D:\project\vueProject\vue-02\src\components\hello.vue 5:5 error Parsing error: x-invalid-end-tag
• [Solved] Parsing error: No Babel config file detected for XXX
• [Solved] Vue Error: Parsing error:No Babel config file detected for xxx
• [Solved] Vue Error: Parsing error: No Babel config file detected for /Users/Usename/xxx…
• Parsing error: await is a reserved word [How to Solve]
• [Solved] Vue Error: Parsing error: No Babel config file detected for
• [Solved] ESLint: Parsing error: Unexpected token(prettier/prettier)
• [Solved] vue Project Error: react lazy eslint error Parsing error: Unexpected token import
• [Solved] Vue-vscode Error: Parsing error: Unexpected reserved word ‘await‘.
• [Solved] Turf.js error: uncaught (in promise) error: the solution of invalid unit
• [Vue warn]: Invalid prop: custom validator check failed for prop “index“
• [Solved] SyntaxError: Invalid regular expression: invalid group specifier name
• [Solved] Vue Less error: Webpack project report expected indentation of 0 spaces but found 2  
• IDEA Project let Report Error [How to Solve]
• [Solved] vue-roter 4 Error: Error: Invalid route component/Uncaught (in promise) Error: Invalid route component
• The page console error [Vue warn]: Invalid prop: custom validator check failed for prop “status“
• Vue: initialize failed: invalid DOM [How to Solve]