After the project is built with Vue/cli, the above error will be reported after startup. The following methods can be used to avoid error reporting:
In the SRC directory, create a vue.config.js file, write the following code in the file, and then restart NPM run serve
module.exports = {
lintOnSave:false
}
Read More:
- How to Solve Vue cli syntax Close Error
- [Solved] error ‘test‘ is assigned a value but never used no-unused-vars
- How to Solve VUE Error: Mixed spaces and tabs
- [Solved] Vue item packaging error: Failed to load resource: the server responded with a status of 404 (Not Found)
- [Solved] Component name “login“ should always be multi-word.
- [Solved] Syntax Error: Error: No ESLint configuration found & TypeError: eslint.CLIEngine is not a constructor
- [Solved] Vue eslint Error: Component name “*****“ should always be multi-word
- vue.config.js build Package UglifyJsPlugin to clear console and print console.log Error: `warnings` is not a supported option
- [Solved] Vue3.0 Error: The component has been registered but not used vue/no-unused-components, Close eslint
- [Solved] vue error: error Component name “School“ should always be multi-word vue/multi-word-component-names
- [Solved] Vue Error: Module build failed: Error: No PostCSS Config found in
- ERROR in [eslint] ESLint is not a constructor (How to Solve)
- [Solved] Prittier format code error: JSON Error in…
- [Solved] VS Code Error: Vetur can‘t find ‘tsconfig.json‘ or ‘jsconfig.json‘
- [Solved] ERROR Error loading vue.config.js: ERROR Error: Command failed: git describe
- [Solved] vue3vite Error: Failed to resolve import “@vue/server-renderer from “src\App.vue“. Does the file exist
- Vue-cli2 sub environment packaging
- 9:13 error Component name “home“ should always be multi-word vue/multi-word-component-names
- VScode vue3 Project vetur Error [How to Solve]
- How to Solve Node start error listen eacces 0.0.0.0:810