Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
@algoan/eslint-config
Advanced tools
Algoan ESLint configuration shared for NodeJS projects written in TypeScript and using prettier. It is the ESLint equivalent for @yelloan/tslint rules.
First, install this module running:
npm install @algoan/eslint-config --save-dev
Then, create a .eslintrc.json
file:
{
"extends": "@algoan/eslint-config"
}
In your package.json
file, add a script:
{
"lint": "eslint src/**/**.ts"
}
Using the tsling-to-eslint-config script:
8 ESLint rules behave differently from their TSLint counterparts:
* @typescript-eslint/no-unused-expressions:
- The TSLint optional config "allow-new" is the default ESLint behavior and will no longer be ignored.
* prefer-arrow/prefer-arrow-functions:
- ESLint does not support allowing named functions defined with the function keyword.
* camelcase:
- Leading undescores in variable names will now be ignored.
* no-underscore-dangle:
- Leading and trailing underscores (_) on identifiers will now be ignored.
* no-redeclare:
- ESLint does not support check-parameters.
* @typescript-eslint/no-unused-vars:
- Please read the following article as the rule behaviour may change on the short term: https://github.com/typescript-eslint/typescript-eslint/issues/1856
* @typescript-eslint/strict-boolean-expressions:
- String, number, enum, and mixed union types are now forbidden.
* class-methods-use-this:
- allow-public methods will no longer be ignored.
15 rules are not known by tslint-to-eslint-config to have ESLint equivalents:
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "completed-docs".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "encoding".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "match-default-export-name".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "no-dynamic-delete".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "no-inferred-empty-object-type".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "no-mergeable-namespace".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "no-unnecessary-callback-wrapper".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "no-unsafe-any".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "prefer-conditional-expression".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "prefer-method-signature".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "prefer-switch".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "return-undefined".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "strict-type-predicates".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "switch-final-break".
* tslint-to-eslint-config does not know the ESLint equivalent for TSLint's "typedef".
FAQs
Algoan ESLint configurations
We found that @algoan/eslint-config demonstrated a healthy version release cadence and project activity because the last version was released less than 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
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.