Set Up for Vue Plugin
Overview
ESLint has a plugin for linting and fixing in Vue projects, eslint-plugin-vue. As the documentation says, ‘this plugin allows us to check the <template>
and <script>
of .vue files with ESLint, as well as Vue code in .js
files’.
We can set up the TypeScript Analyzer to use this plugin in Visual Studio projects. Instructions on how to do this for the Vue projects in Visual Studio are below.
Vue and Visual Studio Projects
Visual Studio has several Vue project templates, of two basic types:
- ‘Standalone Vue Project’ and ‘Vue and ASP.NET Core’ project, both in JavaScript and TypeScript versions. These project templates are only available in Visual Studio 2022. The projects created here are Vue 3. Here the Standalone projects are just client projects, whereas the ‘Vue and ASP.NET Core’ projects have a client project but also a C# ASP.NET Core server project in the created solution.
- ‘Basic vue.js Web Application’. These project templates available in Visual Studio 2017 and 2019, and in JavaScript or TypeScript versions. They used to be in Visual Studio 2022 but have been removed. We recommend you don’t use these templates. They are very old, target Vue 2 which is an old version of Vue, and the npm packages won’t even install with the latest versions of Node. As a result configuring them for use with the TypeScript Analyzer is no longer covered here.
Enabling the TypeScript Analyzer for the ‘Standalone Vue Projects’ and ‘Vue and ASP.NET Core’ projects is described below. The setup process is the same for any of these projects.
Standalone JavaScript/TypeScript Vue Project or Vue and ASP.NET Core Project in Visual Studio 2022
Which Project Are We Setting Up ESLint In?
In the discussion below we will refer to the ‘client project’, which is the JavaScript or TypeScript project in which we are setting up ESLint. With the Standalone projects this is the sole project in the solution. However, as mentioned, with the Vue and ASP.NET Core project we have two projects in our solution: an ASP.NET Core project in C#, which we can’t lint with ESLint because it’s the wrong language, and a JavaScript or TypeScript project. Here, obviously, the client project is the JavaScript or TypeScript project.
Using the Default Linting from a Terminal
If in Visual Studio 2022 you create any of these project types then linting from a terminal window is set up for you as part of the project creation.
ESLint and the eslint-plugin-vue plugin are installed for you, and ESLint is configured via a .eslintrc.cjs file in the root of the project.
If you run npm run lint
from a terminal in the root of the client project ESLint will run and show any errors.
Enabling TypeScript Analyzer To Use the Default Linting
The TypeScript Analyzer can use this ESLint configuration, and show linting errors in the code windows and Error List.
To enable this you need to add .vue files to the list of files the Analyzer handles. To do this go to Tools/Options/TypeScript Analyzer/ESLint and under ‘File extensions to lint’ add ‘,vue’ to the existing list. After the change the ‘File extensions to lint’ setting should look like ‘js,jsx,ts,tsx,mjs,cjs,vue’. All other settings on this screen should be set to the defaults. In particular settings ‘Enable local config’ and ‘Enable local node_modules’ should be set to True.
You also need to have built the solution at least once to ensure it works and to install the npm packages.
Testing This Is Working
To test this is working, open file src/App.vue in the client project. On line 11 currently there is a ‘HelloWorld’ component declared with attribute msg:
<HelloWorld msg="You did it!" />
An easy way to generate an error from the eslint-plugin-vue is to simply duplicate the attribute. That is, change this code to:
<HelloWorld msg="You did it!" msg="You did it!" />
If you do this change you should get a vue/no-duplicate-attributes and a vue/no-parsing-error error on the second msg attribute. As usual, clicking on the Code in the Error List will take you to the documentation for these errors.
Enabling Prettier
Prettier is not enabled by default in these client projects. We can enable it by following the steps below, which extend the existing configuration.
Please note you may not want to do this: Prettier doesn’t work too well with .vue files, and the plugins that attempt to mitigate this have issues on Windows.
- Doubleclick .eslintrc.cjs in Solution Explorer to edit it. Replace the entire contents of the file with the code below.
For a Standalone JavaScript Vue Project:
/* eslint-env node */ module.exports = { root: true, extends: ['plugin:vue/vue3-essential', 'eslint:recommended'], env: { node: true, }, plugins: ['prettier'], parserOptions: { ecmaVersion: 'latest', }, rules: { 'prettier/prettier': [ 'warn', { tabWidth: 2, endOfLine: 'lf', printWidth: 80, semi: true, singleQuote: true, quoteProps: 'as-needed', jsxSingleQuote: false, trailingComma: 'es5', bracketSpacing: true, arrowParens: 'always', }, ], }, };
For a Standalone TypeScript Vue Project:
/* eslint-env node */ require('@rushstack/eslint-patch/modern-module-resolution'); module.exports = { root: true, extends: [ 'plugin:vue/vue3-essential', 'eslint:recommended', '@vue/eslint-config-typescript', ], env: { node: true, }, plugins: ['prettier'], parserOptions: { parser: '@typescript-eslint/parser', ecmaVersion: 'latest', }, rules: { 'prettier/prettier': [ 'warn', { tabWidth: 2, endOfLine: 'lf', printWidth: 80, semi: true, singleQuote: true, quoteProps: 'as-needed', jsxSingleQuote: false, trailingComma: 'es5', bracketSpacing: true, arrowParens: 'always', }, ], }, };
- Doubleclick package.json to open it and add the dependencies below to the end of the devDependencies section and save. These are the additional npm package dependencies that the TypeScript Analyzer needs to get Prettier to run:
"eslint-plugin-prettier": "5.1.3", "prettier": "3.2.5"
- Install the new npm packages. Rightclick the project in Solution Explorer/Open in Terminal, then in the terminal that appears execute the command
npm i
.
Now if you lint a .vue file in the project you will probably get some Prettier warnings. As usual, you can rightclick/Fix TypeScript Analyzer (ESLint) Errors to format the file and remove these errors.