An error occurred while starting the vue project:
1:1 error Component name “Header” should always be multi-word vue/multi-word
The reason is that the nonstandard code (that is, nonstandard naming) is regarded as an error during the syntax check
Solution:
Add the configuration: lintOnSave: false in the vue.config.js file, as follows:
const { defineConfig } = require('@vue/cli-service')
module.exports = defineConfig({
transpileDependencies: true,
lintOnSave: false
})Read More:
- [Solved] vue error: error Component name “School“ should always be multi-word vue/multi-word-component-names
- [Solved] error Component name “xxx“ should always be multi-word vue/multi-word-comp
- 9:13 error Component name “home“ should always be multi-word vue/multi-word-component-names
- [Solved] Vue eslint Error: Component name “*****“ should always be multi-word
- [Solved] Component name “login“ should always be multi-word.
- [Solved] ESlint Create New File Error: Component name “Home” should always be multi-word.
- Parsing error: await is a reserved word [How to Solve]
- Vue3.0 error: Failed to resolve component el-form-item (el element to be unable to be displayed)
- Vue warn]: vue3 element Component emit Pass Event Error
- [Solved] Vue-vscode Error: Parsing error: Unexpected reserved word ‘await‘.
- [Solved] Vue3.0 Error: The component has been registered but not used vue/no-unused-components, Close eslint
- [Solved] webpack Package Error: ERROR in multi ./src/main.js ./dist/bundle.js Module not found: Error: Can‘t resolv
- Vue Error: component has been registered but not used [Two Methods to Solve]
- [Solved] Vue3 Error: Failed to resolve component:xxx
- [Solved] Vue3.2 component computed Error: Write operation failed: computed value is readonly
- Vue element component V-for error [How to Modify)
- [Solved] el-date-picker Error: Avoid mutating a prop directly since the value will be overwritten whenever the parent component re-renders.
- [Solved] VUE eslint Error: Expected linebreaks to be ‘LF‘ but found ‘CRLF
- [Solved] vue-roter 4 Error: Error: Invalid route component/Uncaught (in promise) Error: Invalid route component
- [Solved] Vue3 Configuration routing error: Catch all routes (“*“) must now be defined using a param with a custom regexp.