dxlint

let you and your agents own your linter

import .ts
import rules:recommended

rule es-eqeqeq error
rule es-no-floating-promises

$ dxlint
warn: Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator. [no-floating-promises]
  --> src/save.ts:4:3
  |
4 |   writeFile(path, data);
  |   ^^^^^^^^^^^^^^^^^^^^^^

another linter? ugh...

• it's over 200× faster than eslint+typescript-eslint. because apples to apples requires eslint without its caching enabled, and dxlint's cache is intrinsic. (even without that, it's also twice as fast and significantly less memory hungry)
• and it has almost perfect eslint parity. 99.4% of eslint's and typescript-eslint's test cases give the same result. type-aware rules read your tsconfig.json without running typescript
• everything is overrideable, you own it all. built-in rules are .dx files: override them, tweak them, write your own, or describe a whole new language
• plus a high quality vscode extension too! extremely fast, with diagnostics, with a proper .dx lsp

getting started

npm install --save-dev @inthedark/dxlint

put a .dx at your project root:

import .ts
import rules:recommended

ignore "dist" "src/generated/**"

exit code 1 means errors were found, 2 means the config is broken. 

don't forget to add .dxcache to .gitignore!!!

for more on the basics: docs/basic.md and the rule list.

the language

a rule is a few lines of .dx: where to look, when it is wrong, and optionally the fix

import .ts

in ts_call.callee rule no-alert-calls error "use the notification service instead of {text}" {
  when text == "alert"
}

docs/advanced.md covers the whole language, from rules over the built-in syntax trees to defining your own languages. docs/ts.md covers what the TypeScript library understands: scopes, modules, types and narrowing.

performance

one core (--jobs 1, both pinned to the same core, wall time, measured in one session), on a project with 2,094 .ts files, its complex custom eslint config ported, type-aware rules included:

and remember: this isn't a fair comparison because eslint --cache doesn't work with typescript-eslint! 

also note that by default dxlint uses every core, and is significantly better at that than eslint+typescript-eslint due to no reliance on typescript itself