Update post

Signed-off-by: Cam McHenry <[email protected]>

Author: camchenry

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

@@ -16,14 +16,15 @@ We're excited to announce the alpha release of type-aware linting in Oxlint!
 
 Following our [technical preview in August](/blog/2025-08-17-oxlint-type-aware), we're excited to announce that type-aware linting has reached alpha status. This milestone brings significant improvements in stability, configurability, and rule coverage.
 
-Type-aware linting enables powerful rules like `no-floating-promises`, `no-misused-promises`, and `await-thenable` that catch bugs by understanding TypeScript's type system. With N type-aware rules now available, you can catch entire categories of runtime errors before they happen.
+Type-aware linting enables powerful rules like `no-floating-promises`, `no-misused-promises`, and `await-thenable` that catch bugs by utilizing TypeScript's type system. With 43 type-aware rules now available, you can catch entire categories of runtime errors before they happen.
 
 The alpha release addresses the major limitations from the technical preview:
 
 - **Full rule configuration support** - Configure individual type-aware rules in `.oxlintrc.json`
 - **Disable comment support** - Use `eslint-disable` comments to control type-aware rules
 - **IDE support** - Type-aware linting works in VSCode and other supported editors
 - **Improved stability** - Many crashes and edge cases have been fixed
+- **Better performance** - Less memory used and slightly better rule performance in some cases
 
 While we're still working on performance for very large monorepos and some advanced rules, the alpha is ready for testing in production codebases.
 
@@ -55,16 +56,44 @@ bunx oxlint --type-aware
 
 :::
 
-To try a specific type-aware rule without other configuration:
+To try a specific type-aware rule without other configuration (`tsgolint` must be installed globally or locally already):
 
-```bash
+::: code-group
+
+```sh [npm]
 npx oxlint --type-aware -A all -D typescript/no-floating-promises
 ```
 
+```sh [pnpm]
+pnpx oxlint --type-aware -A all -D typescript/no-floating-promises
+```
+
+```sh [bun]
+bunx oxlint --type-aware -A all -D typescript/no-floating-promises
+```
+
+:::
+
 For more configuration options, see our [usage guide](/docs/guide/usage/linter/type-aware).
 
 ## What's New
 
+### Support for type-checking while linting
+
+`tsgolint` now supports emitting type checking errors from TypeScript while linting. Since type-aware rules already require checking all of the types within a file, we are able to use this existing type information rather than discarding it. This means that in some cases, it is possible to skip doing a separate type-check command altogether (e.g., `tsc --noEmit`), reducing total time spent doing linting and type-checking in CI.
+
+This is an experimental feature, but you can enable it by adding the `--type-check` and `--type-aware` flag to the `oxlint` command:
+
+```
+$ oxlint --type-aware --type-check
+
+  × typescript(TS2322): Type 'number' is not assignable to type 'string'.
+   ╭─[index.ts:1:7]
+ 1 │ const message: string = 1
+   ·       ───────
+   ╰────
+```
+
 ### Rule configuration support in `oxlint`
 
 Type-aware rules that run in `tsgolint` can be configured in `oxlint` just like any other lint rule. For example, you can configure the `no-floating-promises` rule to allow certain safe calls or ignore `void`:
@@ -83,7 +112,9 @@ Type-aware rules that run in `tsgolint` can be configured in `oxlint` just like
 }
 ```
 
-Previously, this would silently fail, but now the configuration is actually passed to `tsgolint` and parsed for the lint rule to use.
+The configuration options are aligned with what `typescript-eslint` supports and documentation can be found in the configuration section for each rule (like [`no-floating-promises`](https://oxc.rs/docs/guide/usage/linter/rules/typescript/no-floating-promises.html#configuration)).
+
+Previously, configuring this rule would silently fail, but now the configuration is actually passed to `tsgolint` and parsed for the lint rule to use.
 
 ### Disable comment support in `oxlint`
 
@@ -96,36 +127,33 @@ Rules that run in `tsgolint` can now be disabled similar to any other `oxlint` r
 [1, 2, 3].map(async x => x + 1);
 ```
 
-Previously, this didn't actually disable the rule, but now it will.
+Previously, this didn't actually disable the rule, but now it will work as expected.
 
 ### More supported rules
 
-The alpha milestone is largely focused on stability and integrating `tsgolint` more closely with `oxlint`, but we've still ported several rules from `typescript-eslint` which you can now use via `oxlint` as well: 
+We've continued to make progress on porting popular rules from `typescript-eslint` which you can now use via `oxlint`. `tsgolint`, combined with `oxlint`, currently supports 43 type-aware rules.
+
+Since the initial preview, support for the following rules has also been added:
 
-- `no-deprecated`
+- `no-deprecated` (one of the most commonly requested rules)
 - `prefer-includes`
 - `strict-boolean-expressions`
 
 ### TypeScript program diagnostics are now reported
 
-Previously, if TypeScript failed to create and parse a program, these errors were not reported which lead to confusion around why linting was not working. Now, we report any issues with creating a program as a diagnostic. For example, if a `tsconfig.json` file contains `baseUrl`, that will be reported now:
+Previously, if TypeScript failed to create and parse a program, these errors were not reported which lead to confusion around why linting was not working. Now, we report any issues with creating a program as a diagnostic, including if there is a configuration issue in the `tsconfig.json` file. 
+
+For example, if a `tsconfig.json` file contains `baseUrl`, that will be reported as an error, since `baseUrl` has been removed from TypeScript:
 
 ```
 $ oxlint --type-aware
 
-  × Invalid tsconfig
-   ╭─[docs/tsconfig.json:1:1]
- 1 │ {
-   · ▲
- 2 │   "compilerOptions": {
-   ╰────
-  help: Non-relative paths are not allowed. Did you forget a leading './'?
-
-  × Invalid tsconfig
-   ╭─[test/ui/tsconfig.json:1:1]
- 1 │ {
-   · ▲
- 2 │   "extends": "../../tsconfig.base.json",
+  × typescript(tsconfig-error): Invalid tsconfig
+   ╭─[tsconfig.json:4:3]
+ 3 │     "compilerOptions": {
+ 4 │         "baseUrl": ".",
+   ·         ─────────
+ 5 │         "experimentalDecorators": true,
    ╰────
   help: Option 'baseUrl' has been removed. Please remove it from your configuration.
         See https://github.com/oxc-project/tsgolint/issues/351 for more information.
@@ -148,7 +176,7 @@ oxlint CLI (Rust)
   └─ Formats and displays results
 
 tsgolint (Go)
-  ├─ Uses typescript-go for type checking
+  ├─ Uses typescript-go directly for type checking
   ├─ Executes type-aware rules
   └─ Returns structured diagnostics
 ```
@@ -157,7 +185,7 @@ This design keeps Oxlint's core fast while leveraging TypeScript's type system t
 
 ### TypeScript Compatibility
 
-`tsgolint` is based on [typescript-go](https://github.com/microsoft/typescript-go), Microsoft's TypeScript v7.0 rewrite in Go, not the original TypeScript compiler.
+`tsgolint` is based on [typescript-go](https://github.com/microsoft/typescript-go), Microsoft's TypeScript v7.0 rewrite in Go, not the original TypeScript compiler. This means that you encounter some features which are no longer supported.
 
 **Important compatibility notes:**