
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.
eslint-config-vazco
Advanced tools
To install simply add this config (along with ESLint and required dependencies) to your project dev-dependencies:
npm install --save-dev babel-eslint
npm install --save-dev eslint
npm install --save-dev eslint-config-vazco
npm install --save-dev eslint-plugin-babel
npm install --save-dev eslint-plugin-react
npm install --save-dev eslint-plugin-vazco
# If you want to use prettier
npm install --save-dev prettier
npm install --save-dev eslint-plugin-prettier
npm install --save-dev eslint-config-prettier
Ready to use one-liner (for default
config):
npm i -D babel-eslint eslint eslint-config-vazco eslint-plugin-babel eslint-plugin-react eslint-plugin-vazco
Ready to use two-liner (for prettier
config), requires npm 5+:
npm i -D eslint-config-vazco
npx install-peerdeps --dev eslint-config-vazco
We recommend to upgrade to ESLint 5, but if you must you can use older dependencies and config from 3.x branch:
To install simply add this config (along with ESLint and required dependencies) to your project dev-dependencies:
Ready to use one-liner (for default
config):
npm i -D babel-eslint eslint eslint-config-vazco@3 eslint-plugin-babel eslint-plugin-react eslint-plugin-vazco
Ready to use two-liner (for prettier
config), requires npm 5+:
npm i -D eslint-config-vazco@3
npx install-peerdeps --dev eslint-config-vazco@3
We strongly recommend to upgrade to ESLint 5, but if you must you can use older dependencies and config from 2.x branch:
npm i -D eslint@3 babel-eslint@7 eslint-config-vazco@2 eslint-plugin-babel@4 eslint-plugin-react@6 eslint-plugin-vazco@1
If you want to use this config with ESLint 2.x (required e.g. for Node 0.10) you can install config for version 1.x:
npm i -D eslint@2 eslint-config-vazco@1 babel-eslint@6 eslint-plugin-babel@3 eslint-plugin-react@5
Extend your project ESLint rules with our config. This can be done in few ways:
{
"extends": "vazco",
"rules": {
// custom project rules
}
}
extends:
- vazco
rules:
// custom project rules
{
"eslintConfig": {
"extends": "vazco"
}
}
vazco/prettier
Prettier is an opinionated code formatter: it removes all styling and enforces outputted code to use a consistent style.
Usage is the same as in examples above, just replace "extends": "vazco"
with "extends": "vazco/prettier"
.
{
"extends": "vazco/prettier"
}
This config is more strict, and using eslint --fix
will completely reformat your code using prettier.
Introducing prettier to project can be problematic. To avoid merge conflicts, all active branches should reformat code at the same time.
Later on code could be --fix
ed on every commit, with tools like lint-staged and pre-commit or husky
All changes introduces in the config are tracked inside changelog file.
All information regarding making changes in the config and versioning details can be found in contributing file.
Please read them before opening a Pull Request or suggesting a change.
Like every package maintained by Vazco, eslint-config-vazco is MIT licensed.
FAQs
ESLint rules used in Vazco.eu projects
We found that eslint-config-vazco demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 7 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
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.