The ESLint custom parser for .vue files.

ESLint supports autofix on custom parsers but does not support autofix on plugins which have processors (eslint/eslint#7510). The motivation of this custom parser is that it supports autofix on .vue files.

$ npm install --save-dev eslint vue-eslint-parser

• vue-eslint-parser requires ESLint 3.5.0 or later.

1. Write parser option in your .eslintrc.* file.
2. Use glob patterns or --ext .vue CLI option.

{
    "extends": "eslint:recommended",
    "parser": "vue-eslint-parser"
}

$ eslint "src/**.{js,vue}"
# or
$ eslint src --ext .vue

parserOptions is the same as what espree, the default parser of ESLint, is supporting. For example:

{
    "parser": "vue-eslint-parser",
    "parserOptions": {
        "sourceType": "module",
        "ecmaVersion": 2017
        // ...
    }
}

On the other hand, you can specify a custom parser to parse <script> tags. In this case, specify parser property. Other properties than parser would be given to the specified parser. For example:

{
    "parser": "vue-eslint-parser",
    "parserOptions": {
        "parser": "babel-eslint",
        "sourceType": "module",
        "allowImportExportEverywhere": false
    }
}

• Those rules are warning code due to the outside of <script> tags. Please disable those rules for .vue files as necessary.
  • eol-last
  • linebreak-style
  • max-len
  • max-lines
  • no-trailing-spaces
  • unicode-bom
• Other rules which are using the source code text instead of AST might be confused as well.

• GitHub Releases

Welcome contributing!

Please use GitHub's Issues/PRs.

• npm test runs tests and measures coverage.
• npm run coverage shows the coverage result of npm test command with the default browser.
• npm run clean removes the coverage result of npm test command.
• npm run lint runs ESLint.
• npm run watch runs tests with --watch option.