# Compiler macros such as defineProps and defineEmits generate no-undef warnings Previously you had to use the vue/script-setup-uses-vars rule, this is no longer needed. You need to use vue-eslint-parser (opens new window) v9.0.0 or later. # Does not work well with # The variables used in the are warned by no-unused-vars rule See also: ' Visual Studio Code' section and Vetur - Linting (opens new window). You need to turn off Vetur's template validation by adding : false to your. Used but the template still show vue/no-parsing-error warnings.Using the comment does not suppress warnings.Turning off the rule in the ESLint configuration file does not ignore the warning.Note that you cannot use angle-bracket type assertion style ( var x = bar ) when using jsx: true. The same configuration is required when using JSX with TypeScript (TSX) in the.

See also ESLint - Specifying Parser Options (opens new window). 'parser': please move it into parserOptions, so it doesn't collide with the vue-eslint-parser used by this plugin's configuration: Make sure you have one of the following settings in your. Most eslint-plugin-vue rules require vue-eslint-parser to check ASTs. Read more: JetBrains - ESLint (opens new window) # ❓ FAQ # What is the 'Use the latest vue-eslint-parser' error? If your ESLint configuration is updated (manually or from your version control), open it in the editor and choose Apply ESLint Code Style Rules in the context menu. On the ESLint page that opens, select the Enable checkbox. In the Settings/Preferences dialog ( Cmd+,/ Ctrl+Alt+S), choose JavaScript under Languages and Frameworks and then choose ESLint under Code Quality Tools. Go into Settings -> Packages -> linter-eslint, under the option 'List of scopes to run eslint on', add.

Jetbrains webstorm.