Cam McHenry

@camchenry.com

556 Followers 314 Following

dad | software engineer @github.com | core team member of oxc.rs | ✝️ camchenry.com

results of running "pnpx oxlint --debug=timings --silent" on the actualbudget/actual repository. It says "Found 22 warnings and 0 errors. Finished in 7.5s on 1805 files using 8 threads." and then includes a rule timings table that lists the slowest rules from slowest to fastest. Each row includes the rule name, time it took to run in milliseconds, relative time, number of times called, and where the rule comes from (source). For example, the eslint/no-unused-vars rule took 297ms (26.8% of total), and was called 1,805 times and is a native rule.
Video shows a file that contains a single error. Then a node version of oxlint is run with the "--suppress-all" flag which adds a suppression to the "oxlint-suppression.json". The suppression is a file path key with an object value that contains the count of suppressed errors grouped by rule. Changing the suppressions file updates the error diagnostic in real time.
Editing an oxlint config file in VS Code, showing that you can change the `ignoreVoid` setting for the `no-floating-promises` rule and get varying diagnostics. This was not previously possible.
Hyperfine benchmark showing that oxlint 1.24 is 1.11 times faster than v1.23, 1.26 times faster than v1.22, and 1.27 times faster than v1.21.
A hyperfine benchmark showed that oxlint 1.24 is 1.03 times faster than v1.23, 1.11 times faster than v1.21, and 1.12 times faster than v1.22.
A benchmark of oxlint runs against the vscode repository. The final summary shows 'pnpx oxlint@1.23 --silent' ran 7% faster than 1.21, 8% faster than 1.22, 9% faster than 1.20, and 9% faster than 1.19. The average time for 1.23 was 844.8ms.
Oxlint linter CodSpeed benchmark showing 65-84% performance improvements
A screenshot of error output in the oxlint CLI. The error message reads: "Optional chain expressions can return undefined by design: using a non-null assertion is unsafe and wrong" and points to the code: "foo?.bar!". The question mark has a label of "optional chain used" and the exclamation mark has a label of "non-null assertion made after optional chain". The help text says to remove the non-null assertion.
A screenshot of a JavaScript file in the VS Code UI. The file contains the expression "foo?.bar!", which has an error associated with it on the question mark, which says "Optional chain expressions can return undefined by design". The user is hovering over the exclamation mark, which has a popup visible on it which says "non-null assertion made after optional chain"
Screenshot of a VSCode editor, with the "quick fix" menu open for a debugger statement in a JavaScript file. The error message says "debugger statement is not allowed" and the top code action says "Remove the debugger statement"
A diff view of a package.json dependencies list, on the left-hand side is a list of the 6 rollup plugins removed plus the rollup dependency. The plugins removed include the commonjs plugin, json plugin, and node-resolve plugin. Now all of that is replaced with just the "rolldown" plugin
A utopian future cityscape
point of view shot from the end of a corgi nose eating the camera
SNL sketch of george washington with nate bergatze as george washington in center, with keenan thompson and james austin johnson as soldiers on right and left, respectively