||7 days ago|
|.circleci||3 weeks ago|
|.github/ISSUE_TEMPLATE||1 year ago|
|.vscode||3 months ago|
|docs||7 days ago|
|eslint-internal-rules||1 month ago|
|lib||7 days ago|
|tests||7 days ago|
|tools||4 months ago|
|typings||3 weeks ago|
|.editorconfig||4 years ago|
|.env-cmdrc||9 months ago|
|.eslintignore||2 years ago|
|.eslintrc.js||1 month ago|
|.gitattributes||4 years ago|
|.gitignore||1 year ago|
|.npmrc||4 years ago|
|.prettierrc||1 year ago|
|LICENSE||4 years ago|
|README.md||11 months ago|
|package.json||7 days ago|
|tsconfig.json||1 year ago|
Official ESLint plugin for Vue.js
See the official website.
⚓ Versioning Policy
This project uses GitHub Releases.
🍻 Contribution Guide
Contribution is welcome!
Working with Rules
Before you start writing a new rule, please read the official ESLint guide.
Next, in order to get an idea how does the AST of the code that you want to check looks like, use the astexplorer.net. The astexplorer.net is a great tool to inspect ASTs, also Vue templates are supported.
After opening astexplorer.net, select
Vue as the syntax and
vue-eslint-parser as the parser.
vue-eslint-parser generates enhanced AST with nodes that represent specific parts of the template syntax, as well as what's inside the
To know more about certain nodes in produced ASTs, go here:
vue-eslint-parser provides a few useful parser services that help traverse the produced AST and access tokens of the template:
Check out an example rule to get a better understanding of how these work.
Please be aware that regarding what kind of code examples you'll write in tests, you'll have to accordingly set up the parser in
RuleTester (you can do it on a per test case basis). See an example here.
If you'll stuck, remember there are plenty of rules you can learn from already. If you can't find the right solution, don't hesitate to reach out in issues – we're happy to help!
See the LICENSE file for license rights and limitations (MIT).