You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Benchmarks were performed on a MacBook Pro M2 Max 12 Cores (8 performance and 4 efficiency).
91
+
92
+
Our performance testing shows that `oxlint` with type-aware linting is around 10 times faster than `eslint` with `typescript-eslint`. Take a look at our [performance benchmarks](https://github.com/oxc-project/bench-linter) for more details.
93
+
94
+
Oxlint can also be used to typecheck your codebase while linting. This avoids a duplicate work, as much of the type information is already computed during type-aware linting..
95
+
96
+
## What's new since the technical preview?
84
97
85
98
### Support for type-checking while linting
86
99
@@ -170,17 +183,6 @@ $ oxlint --type-aware
170
183
171
184
Type-aware rules now support automatic fixes via the `--fix` flag. When you run `oxlint --type-aware --fix`, fixable diagnostics from `tsgolint` are applied just like regular `oxlint` fixes. This brings full parity with non-type-aware rules for the fix workflow.
Benchmarks were performed on a MacBook Pro M2 Max 12 Cores (8 performance and 4 efficiency).
181
-
182
-
Our performance testing shows that `oxlint` with type-aware linting is around 10 times faster that `eslint` with `typescript-eslint`. Take a look at our [performance benchmarks](https://github.com/oxc-project/bench-linter) for more details.
0 commit comments