Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
master
bdeeb036 fix(bundling): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true (#34493) ## Current Behavior In TS Solution Setup, the esbuild executor forces `runTypeCheck` even when `skipTypeCheck: true` and `declaration: false`, due to the `|| options.isTsSolutionSetup` condition in `esbuild.impl.ts` (lines 139-140 and 195). When `declaration: false`, this type check runs in `noEmit` mode with `ignoreDiagnostics: true` — making it **completely pointless** (no declarations emitted, no diagnostics reported). Its only observable effect is writing a poisoned 19-byte tsbuildinfo file that causes race conditions with `tsc --build`. ## Expected Behavior When `skipTypeCheck: true` and `declaration: false`, the esbuild executor should not run type checking at all. The `isTsSolutionSetup` override should only force type checking when declarations actually need to be generated. ## Fix ### Primary: Skip unnecessary type check (`esbuild.impl.ts`) ```diff // Non-watch mode (line 195) - if (!options.skipTypeCheck || options.isTsSolutionSetup) { + if (!options.skipTypeCheck || (options.isTsSolutionSetup && options.declaration)) { // Watch mode (lines 139-140) - options.isTsSolutionSetup + (options.isTsSolutionSetup && options.declaration) ``` Only force type checking in TS Solution Setup when declarations need to be generated. This eliminates the pointless type check entirely. ### Defense-in-depth: Prevent tsbuildinfo in `noEmit` mode (`run-type-check.ts`) ```diff - : { noEmit: true }; + : { noEmit: true, composite: false }; ``` Setting `composite: false` alongside `noEmit: true` prevents TypeScript from writing tsbuildinfo files, protecting against this class of bug from any caller of `runTypeCheck`. ## Why This is Safe | Scenario | Before | After | |----------|--------|-------| | `skipTypeCheck: false`, `declaration: false`, `isTsSolutionSetup: true` | Runs type check (noEmit) | Still runs (`!false \|\| ...` = true) | | `skipTypeCheck: false`, `declaration: true`, `isTsSolutionSetup: true` | Runs type check (emitDeclarationOnly) | Still runs | | `skipTypeCheck: true`, `declaration: true`, `isTsSolutionSetup: true` | normalize.ts overrides skipTypeCheck to false; runs type check | Still runs (same normalization) | | **`skipTypeCheck: true`, `declaration: false`, `isTsSolutionSetup: true`** | **Runs pointless type check (noEmit + ignoreDiagnostics), writes poisoned tsbuildinfo** | **Skipped entirely** | The only behavior change is in the last row — the case where the type check was doing nothing useful but causing harm. ## Related Issue(s) Fixes #34492 --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
by wewelll
Failed
master
bdeeb036 fix(bundling): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true (#34493) ## Current Behavior In TS Solution Setup, the esbuild executor forces `runTypeCheck` even when `skipTypeCheck: true` and `declaration: false`, due to the `|| options.isTsSolutionSetup` condition in `esbuild.impl.ts` (lines 139-140 and 195). When `declaration: false`, this type check runs in `noEmit` mode with `ignoreDiagnostics: true` — making it **completely pointless** (no declarations emitted, no diagnostics reported). Its only observable effect is writing a poisoned 19-byte tsbuildinfo file that causes race conditions with `tsc --build`. ## Expected Behavior When `skipTypeCheck: true` and `declaration: false`, the esbuild executor should not run type checking at all. The `isTsSolutionSetup` override should only force type checking when declarations actually need to be generated. ## Fix ### Primary: Skip unnecessary type check (`esbuild.impl.ts`) ```diff // Non-watch mode (line 195) - if (!options.skipTypeCheck || options.isTsSolutionSetup) { + if (!options.skipTypeCheck || (options.isTsSolutionSetup && options.declaration)) { // Watch mode (lines 139-140) - options.isTsSolutionSetup + (options.isTsSolutionSetup && options.declaration) ``` Only force type checking in TS Solution Setup when declarations need to be generated. This eliminates the pointless type check entirely. ### Defense-in-depth: Prevent tsbuildinfo in `noEmit` mode (`run-type-check.ts`) ```diff - : { noEmit: true }; + : { noEmit: true, composite: false }; ``` Setting `composite: false` alongside `noEmit: true` prevents TypeScript from writing tsbuildinfo files, protecting against this class of bug from any caller of `runTypeCheck`. ## Why This is Safe | Scenario | Before | After | |----------|--------|-------| | `skipTypeCheck: false`, `declaration: false`, `isTsSolutionSetup: true` | Runs type check (noEmit) | Still runs (`!false \|\| ...` = true) | | `skipTypeCheck: false`, `declaration: true`, `isTsSolutionSetup: true` | Runs type check (emitDeclarationOnly) | Still runs | | `skipTypeCheck: true`, `declaration: true`, `isTsSolutionSetup: true` | normalize.ts overrides skipTypeCheck to false; runs type check | Still runs (same normalization) | | **`skipTypeCheck: true`, `declaration: false`, `isTsSolutionSetup: true`** | **Runs pointless type check (noEmit + ignoreDiagnostics), writes poisoned tsbuildinfo** | **Skipped entirely** | The only behavior change is in the last row — the case where the type check was doing nothing useful but causing harm. ## Related Issue(s) Fixes #34492 --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
by wewelll
Succeeded
master
bdeeb036 fix(bundling): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true (#34493) ## Current Behavior In TS Solution Setup, the esbuild executor forces `runTypeCheck` even when `skipTypeCheck: true` and `declaration: false`, due to the `|| options.isTsSolutionSetup` condition in `esbuild.impl.ts` (lines 139-140 and 195). When `declaration: false`, this type check runs in `noEmit` mode with `ignoreDiagnostics: true` — making it **completely pointless** (no declarations emitted, no diagnostics reported). Its only observable effect is writing a poisoned 19-byte tsbuildinfo file that causes race conditions with `tsc --build`. ## Expected Behavior When `skipTypeCheck: true` and `declaration: false`, the esbuild executor should not run type checking at all. The `isTsSolutionSetup` override should only force type checking when declarations actually need to be generated. ## Fix ### Primary: Skip unnecessary type check (`esbuild.impl.ts`) ```diff // Non-watch mode (line 195) - if (!options.skipTypeCheck || options.isTsSolutionSetup) { + if (!options.skipTypeCheck || (options.isTsSolutionSetup && options.declaration)) { // Watch mode (lines 139-140) - options.isTsSolutionSetup + (options.isTsSolutionSetup && options.declaration) ``` Only force type checking in TS Solution Setup when declarations need to be generated. This eliminates the pointless type check entirely. ### Defense-in-depth: Prevent tsbuildinfo in `noEmit` mode (`run-type-check.ts`) ```diff - : { noEmit: true }; + : { noEmit: true, composite: false }; ``` Setting `composite: false` alongside `noEmit: true` prevents TypeScript from writing tsbuildinfo files, protecting against this class of bug from any caller of `runTypeCheck`. ## Why This is Safe | Scenario | Before | After | |----------|--------|-------| | `skipTypeCheck: false`, `declaration: false`, `isTsSolutionSetup: true` | Runs type check (noEmit) | Still runs (`!false \|\| ...` = true) | | `skipTypeCheck: false`, `declaration: true`, `isTsSolutionSetup: true` | Runs type check (emitDeclarationOnly) | Still runs | | `skipTypeCheck: true`, `declaration: true`, `isTsSolutionSetup: true` | normalize.ts overrides skipTypeCheck to false; runs type check | Still runs (same normalization) | | **`skipTypeCheck: true`, `declaration: false`, `isTsSolutionSetup: true`** | **Runs pointless type check (noEmit + ignoreDiagnostics), writes poisoned tsbuildinfo** | **Skipped entirely** | The only behavior change is in the last row — the case where the type check was doing nothing useful but causing harm. ## Related Issue(s) Fixes #34492 --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
by wewelll
Failed
master
bdeeb036 fix(bundling): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true (#34493) ## Current Behavior In TS Solution Setup, the esbuild executor forces `runTypeCheck` even when `skipTypeCheck: true` and `declaration: false`, due to the `|| options.isTsSolutionSetup` condition in `esbuild.impl.ts` (lines 139-140 and 195). When `declaration: false`, this type check runs in `noEmit` mode with `ignoreDiagnostics: true` — making it **completely pointless** (no declarations emitted, no diagnostics reported). Its only observable effect is writing a poisoned 19-byte tsbuildinfo file that causes race conditions with `tsc --build`. ## Expected Behavior When `skipTypeCheck: true` and `declaration: false`, the esbuild executor should not run type checking at all. The `isTsSolutionSetup` override should only force type checking when declarations actually need to be generated. ## Fix ### Primary: Skip unnecessary type check (`esbuild.impl.ts`) ```diff // Non-watch mode (line 195) - if (!options.skipTypeCheck || options.isTsSolutionSetup) { + if (!options.skipTypeCheck || (options.isTsSolutionSetup && options.declaration)) { // Watch mode (lines 139-140) - options.isTsSolutionSetup + (options.isTsSolutionSetup && options.declaration) ``` Only force type checking in TS Solution Setup when declarations need to be generated. This eliminates the pointless type check entirely. ### Defense-in-depth: Prevent tsbuildinfo in `noEmit` mode (`run-type-check.ts`) ```diff - : { noEmit: true }; + : { noEmit: true, composite: false }; ``` Setting `composite: false` alongside `noEmit: true` prevents TypeScript from writing tsbuildinfo files, protecting against this class of bug from any caller of `runTypeCheck`. ## Why This is Safe | Scenario | Before | After | |----------|--------|-------| | `skipTypeCheck: false`, `declaration: false`, `isTsSolutionSetup: true` | Runs type check (noEmit) | Still runs (`!false \|\| ...` = true) | | `skipTypeCheck: false`, `declaration: true`, `isTsSolutionSetup: true` | Runs type check (emitDeclarationOnly) | Still runs | | `skipTypeCheck: true`, `declaration: true`, `isTsSolutionSetup: true` | normalize.ts overrides skipTypeCheck to false; runs type check | Still runs (same normalization) | | **`skipTypeCheck: true`, `declaration: false`, `isTsSolutionSetup: true`** | **Runs pointless type check (noEmit + ignoreDiagnostics), writes poisoned tsbuildinfo** | **Skipped entirely** | The only behavior change is in the last row — the case where the type check was doing nothing useful but causing harm. ## Related Issue(s) Fixes #34492 --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
by wewelll
Succeeded
master
bdeeb036 fix(bundling): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true (#34493) ## Current Behavior In TS Solution Setup, the esbuild executor forces `runTypeCheck` even when `skipTypeCheck: true` and `declaration: false`, due to the `|| options.isTsSolutionSetup` condition in `esbuild.impl.ts` (lines 139-140 and 195). When `declaration: false`, this type check runs in `noEmit` mode with `ignoreDiagnostics: true` — making it **completely pointless** (no declarations emitted, no diagnostics reported). Its only observable effect is writing a poisoned 19-byte tsbuildinfo file that causes race conditions with `tsc --build`. ## Expected Behavior When `skipTypeCheck: true` and `declaration: false`, the esbuild executor should not run type checking at all. The `isTsSolutionSetup` override should only force type checking when declarations actually need to be generated. ## Fix ### Primary: Skip unnecessary type check (`esbuild.impl.ts`) ```diff // Non-watch mode (line 195) - if (!options.skipTypeCheck || options.isTsSolutionSetup) { + if (!options.skipTypeCheck || (options.isTsSolutionSetup && options.declaration)) { // Watch mode (lines 139-140) - options.isTsSolutionSetup + (options.isTsSolutionSetup && options.declaration) ``` Only force type checking in TS Solution Setup when declarations need to be generated. This eliminates the pointless type check entirely. ### Defense-in-depth: Prevent tsbuildinfo in `noEmit` mode (`run-type-check.ts`) ```diff - : { noEmit: true }; + : { noEmit: true, composite: false }; ``` Setting `composite: false` alongside `noEmit: true` prevents TypeScript from writing tsbuildinfo files, protecting against this class of bug from any caller of `runTypeCheck`. ## Why This is Safe | Scenario | Before | After | |----------|--------|-------| | `skipTypeCheck: false`, `declaration: false`, `isTsSolutionSetup: true` | Runs type check (noEmit) | Still runs (`!false \|\| ...` = true) | | `skipTypeCheck: false`, `declaration: true`, `isTsSolutionSetup: true` | Runs type check (emitDeclarationOnly) | Still runs | | `skipTypeCheck: true`, `declaration: true`, `isTsSolutionSetup: true` | normalize.ts overrides skipTypeCheck to false; runs type check | Still runs (same normalization) | | **`skipTypeCheck: true`, `declaration: false`, `isTsSolutionSetup: true`** | **Runs pointless type check (noEmit + ignoreDiagnostics), writes poisoned tsbuildinfo** | **Skipped entirely** | The only behavior change is in the last row — the case where the type check was doing nothing useful but causing harm. ## Related Issue(s) Fixes #34492 --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
by wewelll
Failed
master
bdeeb036 fix(bundling): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true (#34493) ## Current Behavior In TS Solution Setup, the esbuild executor forces `runTypeCheck` even when `skipTypeCheck: true` and `declaration: false`, due to the `|| options.isTsSolutionSetup` condition in `esbuild.impl.ts` (lines 139-140 and 195). When `declaration: false`, this type check runs in `noEmit` mode with `ignoreDiagnostics: true` — making it **completely pointless** (no declarations emitted, no diagnostics reported). Its only observable effect is writing a poisoned 19-byte tsbuildinfo file that causes race conditions with `tsc --build`. ## Expected Behavior When `skipTypeCheck: true` and `declaration: false`, the esbuild executor should not run type checking at all. The `isTsSolutionSetup` override should only force type checking when declarations actually need to be generated. ## Fix ### Primary: Skip unnecessary type check (`esbuild.impl.ts`) ```diff // Non-watch mode (line 195) - if (!options.skipTypeCheck || options.isTsSolutionSetup) { + if (!options.skipTypeCheck || (options.isTsSolutionSetup && options.declaration)) { // Watch mode (lines 139-140) - options.isTsSolutionSetup + (options.isTsSolutionSetup && options.declaration) ``` Only force type checking in TS Solution Setup when declarations need to be generated. This eliminates the pointless type check entirely. ### Defense-in-depth: Prevent tsbuildinfo in `noEmit` mode (`run-type-check.ts`) ```diff - : { noEmit: true }; + : { noEmit: true, composite: false }; ``` Setting `composite: false` alongside `noEmit: true` prevents TypeScript from writing tsbuildinfo files, protecting against this class of bug from any caller of `runTypeCheck`. ## Why This is Safe | Scenario | Before | After | |----------|--------|-------| | `skipTypeCheck: false`, `declaration: false`, `isTsSolutionSetup: true` | Runs type check (noEmit) | Still runs (`!false \|\| ...` = true) | | `skipTypeCheck: false`, `declaration: true`, `isTsSolutionSetup: true` | Runs type check (emitDeclarationOnly) | Still runs | | `skipTypeCheck: true`, `declaration: true`, `isTsSolutionSetup: true` | normalize.ts overrides skipTypeCheck to false; runs type check | Still runs (same normalization) | | **`skipTypeCheck: true`, `declaration: false`, `isTsSolutionSetup: true`** | **Runs pointless type check (noEmit + ignoreDiagnostics), writes poisoned tsbuildinfo** | **Skipped entirely** | The only behavior change is in the last row — the case where the type check was doing nothing useful but causing harm. ## Related Issue(s) Fixes #34492 --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
by wewelll
Succeeded
master
bdeeb036 fix(bundling): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true (#34493) ## Current Behavior In TS Solution Setup, the esbuild executor forces `runTypeCheck` even when `skipTypeCheck: true` and `declaration: false`, due to the `|| options.isTsSolutionSetup` condition in `esbuild.impl.ts` (lines 139-140 and 195). When `declaration: false`, this type check runs in `noEmit` mode with `ignoreDiagnostics: true` — making it **completely pointless** (no declarations emitted, no diagnostics reported). Its only observable effect is writing a poisoned 19-byte tsbuildinfo file that causes race conditions with `tsc --build`. ## Expected Behavior When `skipTypeCheck: true` and `declaration: false`, the esbuild executor should not run type checking at all. The `isTsSolutionSetup` override should only force type checking when declarations actually need to be generated. ## Fix ### Primary: Skip unnecessary type check (`esbuild.impl.ts`) ```diff // Non-watch mode (line 195) - if (!options.skipTypeCheck || options.isTsSolutionSetup) { + if (!options.skipTypeCheck || (options.isTsSolutionSetup && options.declaration)) { // Watch mode (lines 139-140) - options.isTsSolutionSetup + (options.isTsSolutionSetup && options.declaration) ``` Only force type checking in TS Solution Setup when declarations need to be generated. This eliminates the pointless type check entirely. ### Defense-in-depth: Prevent tsbuildinfo in `noEmit` mode (`run-type-check.ts`) ```diff - : { noEmit: true }; + : { noEmit: true, composite: false }; ``` Setting `composite: false` alongside `noEmit: true` prevents TypeScript from writing tsbuildinfo files, protecting against this class of bug from any caller of `runTypeCheck`. ## Why This is Safe | Scenario | Before | After | |----------|--------|-------| | `skipTypeCheck: false`, `declaration: false`, `isTsSolutionSetup: true` | Runs type check (noEmit) | Still runs (`!false \|\| ...` = true) | | `skipTypeCheck: false`, `declaration: true`, `isTsSolutionSetup: true` | Runs type check (emitDeclarationOnly) | Still runs | | `skipTypeCheck: true`, `declaration: true`, `isTsSolutionSetup: true` | normalize.ts overrides skipTypeCheck to false; runs type check | Still runs (same normalization) | | **`skipTypeCheck: true`, `declaration: false`, `isTsSolutionSetup: true`** | **Runs pointless type check (noEmit + ignoreDiagnostics), writes poisoned tsbuildinfo** | **Skipped entirely** | The only behavior change is in the last row — the case where the type check was doing nothing useful but causing harm. ## Related Issue(s) Fixes #34492 --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
by wewelll
Failed
master
bdeeb036 fix(bundling): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true (#34493) ## Current Behavior In TS Solution Setup, the esbuild executor forces `runTypeCheck` even when `skipTypeCheck: true` and `declaration: false`, due to the `|| options.isTsSolutionSetup` condition in `esbuild.impl.ts` (lines 139-140 and 195). When `declaration: false`, this type check runs in `noEmit` mode with `ignoreDiagnostics: true` — making it **completely pointless** (no declarations emitted, no diagnostics reported). Its only observable effect is writing a poisoned 19-byte tsbuildinfo file that causes race conditions with `tsc --build`. ## Expected Behavior When `skipTypeCheck: true` and `declaration: false`, the esbuild executor should not run type checking at all. The `isTsSolutionSetup` override should only force type checking when declarations actually need to be generated. ## Fix ### Primary: Skip unnecessary type check (`esbuild.impl.ts`) ```diff // Non-watch mode (line 195) - if (!options.skipTypeCheck || options.isTsSolutionSetup) { + if (!options.skipTypeCheck || (options.isTsSolutionSetup && options.declaration)) { // Watch mode (lines 139-140) - options.isTsSolutionSetup + (options.isTsSolutionSetup && options.declaration) ``` Only force type checking in TS Solution Setup when declarations need to be generated. This eliminates the pointless type check entirely. ### Defense-in-depth: Prevent tsbuildinfo in `noEmit` mode (`run-type-check.ts`) ```diff - : { noEmit: true }; + : { noEmit: true, composite: false }; ``` Setting `composite: false` alongside `noEmit: true` prevents TypeScript from writing tsbuildinfo files, protecting against this class of bug from any caller of `runTypeCheck`. ## Why This is Safe | Scenario | Before | After | |----------|--------|-------| | `skipTypeCheck: false`, `declaration: false`, `isTsSolutionSetup: true` | Runs type check (noEmit) | Still runs (`!false \|\| ...` = true) | | `skipTypeCheck: false`, `declaration: true`, `isTsSolutionSetup: true` | Runs type check (emitDeclarationOnly) | Still runs | | `skipTypeCheck: true`, `declaration: true`, `isTsSolutionSetup: true` | normalize.ts overrides skipTypeCheck to false; runs type check | Still runs (same normalization) | | **`skipTypeCheck: true`, `declaration: false`, `isTsSolutionSetup: true`** | **Runs pointless type check (noEmit + ignoreDiagnostics), writes poisoned tsbuildinfo** | **Skipped entirely** | The only behavior change is in the last row — the case where the type check was doing nothing useful but causing harm. ## Related Issue(s) Fixes #34492 --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
by wewelll
Succeeded
master
bdeeb036 fix(bundling): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true (#34493) ## Current Behavior In TS Solution Setup, the esbuild executor forces `runTypeCheck` even when `skipTypeCheck: true` and `declaration: false`, due to the `|| options.isTsSolutionSetup` condition in `esbuild.impl.ts` (lines 139-140 and 195). When `declaration: false`, this type check runs in `noEmit` mode with `ignoreDiagnostics: true` — making it **completely pointless** (no declarations emitted, no diagnostics reported). Its only observable effect is writing a poisoned 19-byte tsbuildinfo file that causes race conditions with `tsc --build`. ## Expected Behavior When `skipTypeCheck: true` and `declaration: false`, the esbuild executor should not run type checking at all. The `isTsSolutionSetup` override should only force type checking when declarations actually need to be generated. ## Fix ### Primary: Skip unnecessary type check (`esbuild.impl.ts`) ```diff // Non-watch mode (line 195) - if (!options.skipTypeCheck || options.isTsSolutionSetup) { + if (!options.skipTypeCheck || (options.isTsSolutionSetup && options.declaration)) { // Watch mode (lines 139-140) - options.isTsSolutionSetup + (options.isTsSolutionSetup && options.declaration) ``` Only force type checking in TS Solution Setup when declarations need to be generated. This eliminates the pointless type check entirely. ### Defense-in-depth: Prevent tsbuildinfo in `noEmit` mode (`run-type-check.ts`) ```diff - : { noEmit: true }; + : { noEmit: true, composite: false }; ``` Setting `composite: false` alongside `noEmit: true` prevents TypeScript from writing tsbuildinfo files, protecting against this class of bug from any caller of `runTypeCheck`. ## Why This is Safe | Scenario | Before | After | |----------|--------|-------| | `skipTypeCheck: false`, `declaration: false`, `isTsSolutionSetup: true` | Runs type check (noEmit) | Still runs (`!false \|\| ...` = true) | | `skipTypeCheck: false`, `declaration: true`, `isTsSolutionSetup: true` | Runs type check (emitDeclarationOnly) | Still runs | | `skipTypeCheck: true`, `declaration: true`, `isTsSolutionSetup: true` | normalize.ts overrides skipTypeCheck to false; runs type check | Still runs (same normalization) | | **`skipTypeCheck: true`, `declaration: false`, `isTsSolutionSetup: true`** | **Runs pointless type check (noEmit + ignoreDiagnostics), writes poisoned tsbuildinfo** | **Skipped entirely** | The only behavior change is in the last row — the case where the type check was doing nothing useful but causing harm. ## Related Issue(s) Fixes #34492 --------- Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
by wewelll
Failed
34493
Fix applied→
505473ee fix(esbuild): skip unnecessary type-check in TS Solution Setup when skipTypeCheck is true In TS Solution Setup, the esbuild executor forces runTypeCheck even when skipTypeCheck: true and declaration: false. This runs a type check in noEmit mode that suppresses all diagnostics (via ignoreDiagnostics: true), making it completely pointless -- except for its harmful side effect of writing a poisoned 19-byte tsbuildinfo file that causes race conditions with tsc --build. Primary fix (esbuild.impl.ts): Only force type-check in TS Solution Setup when declarations actually need to be generated (isTsSolutionSetup && declaration). When skipTypeCheck is true and declaration is false, the type check is skipped entirely. Defense-in-depth (run-type-check.ts): Also set composite: false in the noEmit code path to prevent tsbuildinfo writes from any caller, since composite: true + noEmit: true still triggers TypeScript to write a minimal tsbuildinfo file.
by wewelll