Research
Security News
Malicious npm Package Targets Solana Developers and Hijacks Funds
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
@isentinel/eslint-config
Advanced tools
npm i -D eslint @isentinel/eslint-config
With "type": "module"
in package.json
(recommended):
// eslint.config.ts
import style from "@isentinel/eslint-config";
export default style();
Note that
.eslintignore
no longer works in Flat config, see customization for more details.
[!TIP] ESLint only detects
eslint.config.js
as the flat config entry, meaning you need to puttype: module
in yourpackage.json
.eslint.config.ts
, you can installeslint-ts-patch
to fix it.
For example:
{
"scripts": {
"lint": "eslint .",
"lint:fix": "eslint . --fix"
}
}
Install VS Code ESLint extension
Add the following settings to your .vscode/settings.json
:
{
// Enable the ESlint flat config support
"eslint.experimental.useFlatConfig": true,
"editor.formatOnSave": false,
// Auto fix
"editor.codeActionsOnSave": {
"source.fixAll.eslint": "always",
"source.organizeImports": "never"
},
// Silent the stylistic rules in you IDE, but still auto fix them
"eslint.rules.customizations": [
{ "rule": "style/*", "severity": "off" },
{ "rule": "format/*", "severity": "off" },
{ "rule": "*-indent", "severity": "off" },
{ "rule": "*-spacing", "severity": "off" },
{ "rule": "*-spaces", "severity": "off" },
{ "rule": "*-order", "severity": "off" },
{ "rule": "*-dangle", "severity": "off" },
{ "rule": "*-newline", "severity": "off" },
{ "rule": "*quotes", "severity": "off" },
{ "rule": "*semi", "severity": "off" }
],
// Enable eslint for all supported languages
"eslint.validate": [
"typescript",
"typescriptreact",
"markdown",
"json",
"jsonc",
"yaml"
]
}
Normally you only need to import the style
preset:
// eslint.config.ts
import style from "@isentinel/eslint-config";
export default style();
And that's it! Or you can configure each integration individually, for example:
// eslint.config.ts
import style from "@isentinel/eslint-config";
export default style({
// `.eslintignore` is no longer supported in Flat config, use `ignores`
// instead
ignores: [
"./fixtures",
// ...globs
],
// Provide TypeScript parser options for access to type checking lints.
typescript: {
parserOptions: {
ecmaVersion: 2018,
jsx: true,
sourceType: "module",
useJSXTextNode: true,
},
tsconfigPath: "./tsconfig.json",
},
// Disable yaml support
yaml: false,
});
The style
factory function also accepts any number of arbitrary custom config overrides:
// eslint.config.ts
import style from "@isentinel/eslint-config";
export default style(
{
// Configures for isentinel's config
},
// From the second arguments they are ESLint Flat Configs
// you can have multiple configs
{
files: ["**/*.ts"],
rules: {},
},
{
rules: {},
},
);
Check out the configs and factory for more details.
Thanks to antfu/eslint-config and sxzz/eslint-config for the inspiration and reference.
Since flat config requires us to explicitly provide the plugin names (instead of the mandatory convention from npm package name), we renamed some plugins to make the overall scope more consistent and easier to write.
New Prefix | Original Prefix | Source Plugin |
---|---|---|
import/* | i/* | eslint-plugin-i |
node/* | n/* | eslint-plugin-n |
yaml/* | yml/* | eslint-plugin-yml |
ts/* | @typescript-eslint/* | @typescript-eslint/eslint-plugin |
style/* | @stylistic/* | @stylistic/eslint-plugin |
When you want to override rules, or disable them inline, you need to update to the new prefix:
-// eslint-disable-next-line @typescript-eslint/consistent-type-definitions
+// eslint-disable-next-line ts/consistent-type-definitions
type foo = { bar: 2 }
We provide some optional configs for specific use cases, that we don't include their dependencies by default.
To enable React support, you need to explicitly turn it on:
// eslint.config.ts
import style from "@isentinel/eslint-config";
export default style({
react: true,
});
Running npx eslint
should prompt you to install the required dependencies, otherwise, you can install them manually:
npm i -D eslint-plugin-react eslint-plugin-react-hooks
This config also provides some optional plugins/rules for extended usages.
perfectionist
(sorting)This plugin eslint-plugin-perfectionist
allows you to sorted object keys, imports, etc, with auto-fix.
The plugin is installed and some rules are enabled by default, but these rules can be disabled or overridden by your own config. For example, I personally have sort-objects set to:
// eslint.config.ts
import style from "@isentinel/eslint-config";
export default style({
rules: {
"perfectionist/sort-objects": [
"warn",
{
"custom-groups": {
id: "id",
name: "name",
"react-props": ["children", "ref"],
},
groups: ["id", "name", "unknown", "react-props"],
order: "asc",
"partition-by-comment": "Part:**",
type: "natural",
},
],
},
});
If you want to apply lint and auto-fix before every commit, you can add the following to your package.json
:
{
"simple-git-hooks": {
"pre-commit": "npm lint-staged"
},
"lint-staged": {
"*": "eslint --fix"
}
}
and then
npm i -D lint-staged simple-git-hooks
There is a visual tool to help you view what rules are enabled in your project and apply them to what files, eslint-flat-config-viewer
Go to your project root that contains eslint.config.ts
and run:
npx eslint-flat-config-viewer
Sure, you can configure and override rules locally in your project to fit your needs. If that still does not work for you, you can always fork this repo and maintain your own. I am open to PRs that help improve the overall experience for developers, and there may still be rules activated that do not apply to the roblox-ts ecosystem.
FAQs
iSentinel's ESLint config
We found that @isentinel/eslint-config demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.
Research
Security News
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.