
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
atom-eslint-parser
Advanced tools
The ESLint custom parser for .atom
files.
npm install eslint atom-eslint-parser --save
atom-eslint-parser
requires ESLint 3.9.0 or later.parser
option into your .eslintrc.*
file.--ext .atom
CLI option.{
"extends": "eslint:recommended",
"parser": "atom-eslint-parser"
}
$ eslint "src/**/*.{atom}"
# or
$ eslint src --ext .atom
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"
}
}
babel-eslint
, it has additional requirements. Use eslint@>=4.14.0
and babel-eslint@>=8.1.1
.typescript-eslint-parser
, the location of original nodes can be wrong. Waiting for typescript-eslint-parser
to support parseResult.visitorKeys.parserServices
to traverse <template>
.
defineTemplateBodyVisitor(templateVisitor, scriptVisitor)
... returns ESLint visitor to traverse <template>
.getTemplateBodyTokenStore()
... returns ESLint TokenStore
to get the tokens of <template>
.<template>
AST specification.Some rules make warnings due to the outside of <script>
tags.
Please disable those rules for .atom
files as necessary.
npm test
runs tests and measures coverage.npm run build
compiles TypeScript source code to index.js
, index.js.map
, and index.d.ts
.npm run coverage
shows the coverage result of npm test
command with the default browser.npm run clean
removes the temporary files which are created by npm test
and npm run build
.npm run lint
runs ESLint.npm run setup
setups submodules to develop.npm run update-fixtures
updates files in test/fixtures/ast
directory based on test/fixtures/ast/*/source.atom
files.npm run watch
runs build
, update-fixtures
, and tests with --watch
option.FAQs
The ESLint custom parser for `.atom` files.
The npm package atom-eslint-parser receives a total of 1 weekly downloads. As such, atom-eslint-parser popularity was classified as not popular.
We found that atom-eslint-parser demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.