0.0.9 • Published 4 years ago
atom-eslint-parser v0.0.9
atom-eslint-parser
The ESLint custom parser for .atom files.
Installation
npm install eslint atom-eslint-parser --saveatom-eslint-parserrequires ESLint 3.9.0 or later.
Usage
- Write
parseroption into your.eslintrc.*file. - Use glob patterns or
--ext .atomCLI option.
{
"extends": "eslint:recommended",
"parser": "atom-eslint-parser"
}$ eslint "src/**/*.{atom}"
# or
$ eslint src --ext .atomOptions
parserOptions has the same properties as what espree, the default parser of ESLint, is supporting.
For example:
{
"parser": "atom-eslint-parser",
"parserOptions": {
"sourceType": "module",
"ecmaVersion": 2017,
"ecmaFeatures": {
"globalReturn": false,
"impliedStrict": false,
"jsx": false,
"experimentalObjectRestSpread": false
}
}
}Also, you can use parser property to specify a custom parser to parse <script> tags.
Other properties than parser would be given to the specified parser.
For example:
{
"parser": "atom-eslint-parser",
"parserOptions": {
"parser": "babel-eslint",
"sourceType": "module",
"allowImportExportEverywhere": false
}
}{
"parser": "atom-eslint-parser",
"parserOptions": {
"parser": "typescript-eslint-parser"
}
}- If you use with
babel-eslint, it has additional requirements. Useeslint@>=4.14.0andbabel-eslint@>=8.1.1. - If you use
typescript-eslint-parser, the location of original nodes can be wrong. Waiting fortypescript-eslint-parserto support parseResult.visitorKeys.
Usage for custom rules / plugins
- This parser provides
parserServicesto traverse<template>.defineTemplateBodyVisitor(templateVisitor, scriptVisitor)... returns ESLint visitor to traverse<template>.getTemplateBodyTokenStore()... returns ESLintTokenStoreto get the tokens of<template>.
- ast.md is
<template>AST specification.
Known Limitations
Some rules make warnings due to the outside of <script> tags.
Please disable those rules for .atom 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.
Development Tools
npm testruns tests and measures coverage.npm run buildcompiles TypeScript source code toindex.js,index.js.map, andindex.d.ts.npm run coverageshows the coverage result ofnpm testcommand with the default browser.npm run cleanremoves the temporary files which are created bynpm testandnpm run build.npm run lintruns ESLint.npm run setupsetups submodules to develop.npm run update-fixturesupdates files intest/fixtures/astdirectory based ontest/fixtures/ast/*/source.atomfiles.npm run watchrunsbuild,update-fixtures, and tests with--watchoption.