Skip to content

Commit d768828

Browse files
committed
move known issues section up into performance section
1 parent 5b8927a commit d768828

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/blog/2025-12-01-type-aware-alpha.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -93,6 +93,10 @@ Our performance testing shows that `oxlint` with type-aware linting is around 10
9393

9494
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..
9595

96+
:::warning Known Issues
97+
While `tsgolint` is ready for testing in production codebases, you may encounter issues with running out of memory when working with very large codebases. We are working on optimizing the memory usage for the next milestone. We would love if you tried `tsgolint` and reported any out-of-memory issues to us in the [`tsgolint` repository](https://github.com/oxc-project/tsgolint) and included some details about your project to help us improve memory usage.
98+
:::
99+
96100
## What's new since the technical preview?
97101

98102
### Support for type-checking while linting
@@ -222,10 +226,6 @@ If you're using deprecated features from TypeScript 6.0 or earlier, you'll need
222226

223227
Our typescript-go fork is synced regularly using renovatebot, ensuring we stay current with the latest improvements and fixes. Once TypeScript 7.0 is officially released, we will track stable releases rather than the tip of the main branch.
224228

225-
### Known issues
226-
227-
While `tsgolint` is ready for testing in production codebases, you may encounter issues with running out of memory when working with very large codebases. We are working on optimizing the memory usage for the next milestone. We would love if you tried `tsgolint` and reported any out-of-memory issues to us in the [`tsgolint` repository](https://github.com/oxc-project/tsgolint) and included some details about your project to help us improve memory usage.
228-
229229
## What's next
230230

231231
We're actively working on the following improvements for the beta release:

0 commit comments

Comments
 (0)