Please upgrade the babel-eslint package to version 10.0.3. This will most likely fix those false-positives where vars are used inside loops and wrongly reported as unused.
Official scaffolded Vue CLI project’s configurations After Vue CLI 4.2 upgrades in create project scaffolding in February 2020, you are half way through the configurations by creating a new project with global vue create myproject command and making at least these selections (configurations included below): Vue CLI v4.2.2 ? Please pick a preset: Manually select … Read more
I found another solution for functional components – you can just use React.FC, which provides type checking and autocomplete for static properties like defaultProps. const Hello: React.FC<{name: string, gretting: string}> = ({ name, gretting = ‘night’ }) => In that case you don’t have to use interface at all. But in case you want for … Read more
I’ve found it myself by using another number than 0,1 or 2. I defines the severity of a rule. Severity should be one of the following: 0 = off, 1 = warning, 2 = error (you passed “3”). Documentation: https://eslint.org/docs/user-guide/configuring/rules
.eslintrc.js parserOptions: { parser: ‘babel-eslint’, sourceType: ‘module’, allowImportExportEverywhere: true } Should Be: parser: ‘babel-eslint’, parserOptions: { sourceType: ‘module’, allowImportExportEverywhere: true } Source: https://eslint.org/docs/user-guide/configuring#specifying-parser With (@vue/cli) .eslintrc.json { “parser”: “vue-eslint-parser”, “parserOptions”: { “parser”: “babel-eslint”, “ecmaVersion”: 8, “sourceType”: “module” } }
As far as I know, for now, there isn’t an option for doing so. When your arguments get over the printWidth ( default 80), prettier will break each argument into a separate line. One way could be to increase the printWidth option so that your arguments stay on the same line. The prettier documentation mentions … Read more
Using ESLint from the CLI should fix it: eslint –fix “C:\code\hello-world.js” ESLint CLI documentation
You need to point that field to the actual ESLint script. This would usually be the place where you’ve installed the ESLint npm package or command-line tool.
In addition to @Barmar answer, you could also use prettier configuration on a .eslintrc.js file using the following, property: rules: { // … ‘prettier/prettier’: [‘error’, { singleQuote: true }] }
inside your .eslintrc.json { “rules”: { “quotes”: [ 2, “double” ] }, “overrides”: [ { “files”: [ “src/**/*.js” ], “rules”: { “quotes”: [ 2, “single” ] } } ] } in .eslintignore /someFolder /anotherFolder /oneMoreFolder