One day, while working on one of my Vue projects, I noticed that Eslint started causing build issues by flagging errors such as "Strings must use singlequote" or "Variable declared but never used". Surprisingly, the formatting errors were not being automatically corrected as they should have been. I couldn't pinpoint the exact moment this problem arose or what triggered it, but it may have occurred after running an npm install.
I came across various suggestions to resolve this issue by adding emitWarning: true to the eslint configuration, but unfortunately, this did not work for me.
It appeared that occasionally, the initial build attempt would succeed without any errors but only upon making changes in the code, saving, and restarting the server would the errors be "detected" and thrown. Additionally, Eslint seemed to only focus on files that were currently open in VS Code; when a file was closed and reopened, Eslint no longer flagged formatting issues in that file.
Below is the content of my .eslintrc.js:
module.exports = {
root: true,
env: {
node: true,
"es6": true
},
extends: [
"plugin:vue/essential",
"@vue/standard"
],
rules: {
"no-console": process.env.NODE_ENV === "production" ? "error" : "off",
"no-debugger": process.env.NODE_ENV === "production" ? "error" : "off",
"indent": ["error", 4],
"semi": ["error", "always"],
"space-before-function-paren": ["error", "never"],
"quotes": ["error", "single"]
},
parserOptions: {
parser: "babel-eslint",
sourceType: "module",
ecmaVersion: 6,
emitWarning: true, // tried with and without this
emitError: false, // tried with and without this
failOnError: false, // tried with and without this
failOnWarning: false // tried with and without this
}
};
My other Vue project is functioning properly, and I couldn't identify any significant differences in the setup. How can I prevent Eslint from disrupting builds? What other issues could be at play here? Any assistance would be greatly appreciated!