
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
@kellerkinder/eslint-config
Advanced tools
This package provides the Kellerkinder ESLint configuration for JavaScript, TypeScript and Vue 3. It is based on the AirBnB Configuration with slight alterations.
This config has been developed and tested with the following requirements:
In order to use this configuration, run the following scripts in your NodeJS project:
npm i -D eslint @kellerkinder/eslint-config
You can use this configuration by creating an .eslintrc.json
inside your
project's root directory that is extending this configuration.
{
"extends": "@kellerkinder/eslint-config"
}
You can now execute eslint by running the following script:
npx eslint src/
The src/
directory can be replaced with the directory or file you want to lint.
If you want ESLint to try to fix the errors it found, execute the following command:
npx eslint src/ --fix
Alternatively, refer to your IDE's documentation to find out, if and how ESLint is integrated.
If you are using babel in your project, you can provide ESLint with your own configuration file, by adding this section to your ESLint config:
{
"parserOptions": {
"babelOptions": {
"configFile": "path/to/your/.babelrc"
}
}
}
By default, this configuration comes with babel support for class properties. So unless other babel features are required, you can safely omit this part of the configuration.
If you are working with a TypeScript codebase, you want to change your .eslintrc.json
to extend
the @kellerkinder/eslint-config/typescript
config instead, making it look like this:
{
"extends": "@kellerkinder/eslint-config/typescript"
}
This configuration contains all the rules from the default configuration and extends it by some TypeScript-specific rules.
If you are working with a Vue 3 application, you want to change your .eslintrc.json
to extend
the @kellerkinder/eslint-config/vue
config instead, making it look like this:
{
"extends": "@kellerkinder/eslint-config/vue"
}
Using the Vue 3 configuration automatically assumes that you are using TypeScript as well.
This project features basic configuration tests using Vitest. Tests are automatically execute on push and before publishing. To execute the tests manually, use the following command:
npm test
Linter
is not a constructorThis error is known to be caused by an empty .eslintignore
file.
To solve this, either make sure that your .eslintignore
contains at
least one entry or is removed entirely.
In order to publish a new version of this package on npm, follow these steps:
main
Now, GitHub Actions will build and publish the new version on npm.
This project adheres to Semantic Versioning. Please refer to the CHANGELOG.md for detailed changes and migration instructions.
MIT
FAQs
Kellerkinder ESLint configuration
We found that @kellerkinder/eslint-config demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.