eslint-config-pv
Advanced tools
pro!vision ESLint configuration. Can be adapted and adjusted in each project.
This package provides pro!vision's ESLint configuration as an extensible shared config.
Inspired by Airbnb
This is version >= 2.0.0 of eslint-config-pv, which is compatible with eslint >= 4.0.0. I you are using eslint 3, use eslint-config-pv 1.0.10
npm install --save-dev eslint-config-pv
# for the eslint 3 compatible version
npm install --save-dev eslint-config-pv@1.0.10
We export two ESLint configurations for usage in projects.
Our default export contains all of our ESLint rules, including ECMAScript 6 / ES2015.
Add "extends": "pv" to your .eslintrc:
{
"extends": "pv",
"rules": {
// additional rules here
},
"env": {
// ... add more environments
}
}
Use the legacy sub package if you only want to lint ES5 and below.
{
"extends": "pv/legacy",
"rules": {
// additional rules here
}
}
See the ESlint config docs for more information.
Ensure you are using node >= 4.5 and you have installed eslint and eslint-plugin-import globally:
# node version should be at least 4.5
node -v
# install necessary modules globally
npm install -g eslint eslint-plugin-import
Now you can follow the instructions here
Keep in mind that WebStorm pass all JavaScript files (starting from project root) to eslint. To prevent directories
from being linted, mark them as Excluded. Go to project structure and right click on the directory to be excluded ->
Mark Directory as -> Excluded. Special directories, such as node_modules are marked automatically as library root
and will be excluded by default.
Alternatively, you can define .eslintignore as described here.
2.0.0
"array-bracket-newline": ["off"]"array-element-newline": ["off"]"capitalized-comments": ["off"]"class-methods-use-this": ["off"]"for-direction": ["error"]"func-call-spacing": ["error", "never"]"func-name-matching": ["off"]"indent": ["error", 2, { "SwitchCase": 1 }]"line-comment-position": ["off"]"linebreak-style": ["error", "unix"]"multiline-ternary": ["error", "always-multiline"]"newline-before-return": ["off"]"no-mixed-operators": ["error"]"no-restricted-globals": ["error", "event"]"no-shadow": ["error", { "hoist": "functions" }]"no-warning-comments": ["error", { "terms": ["todo", "fixme", "hack", "hacky"], "location": "start" }]"object-curly-newline": ["off"]"padding-line-between-statements": ["off"]"prefer-destructuring": ["off"]"prefer-promise-reject-errors": ["off"]"require-jsdoc": ["off"]"rest-spread-spacing": ["error", "never"]"semi-style": ["error", "last"]"symbol-description": ["error"]"template-tag-spacing": ["error", "never"]"unicode-bom": ["error", "never"]"getter-return": ["error"]"function-paren-newline": ["off"]FAQs
pro!vision ESLint configuration. Can be adapted and adjusted in each project.
The npm package eslint-config-pv receives a total of 518 weekly downloads. As such, eslint-config-pv popularity was classified as not popular.
We found that eslint-config-pv demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers 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
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.