Benchmark suggestions

General criteria

A benchmark:

• Must be compile with a simple npm|yarn|pnpm install and tsc -p or tsc -b. No funky build systems, no random external artifacts if possible.
  • Compiling with -p is preferred, to prevent fail-fast behavior.
  • Emitting with tsc is even better. Especially declaration emit
• Should compile in less than 60 seconds or so. If you have a benchmark and it takes like 5 minutes to build, that deserves a bug!

Potential candidates

Pulling this list out of https://github.com/microsoft/TypeScript/issues/44033

• webpack (checked JS)
• mongoose
• styled-components
• @emotion/*
• fp-ts
• aws-sdk
• bunp
• artificial auto-imports benchmark (tsserver)
• prisma
• zod
• Code like in https://github.com/microsoft/TypeScript/issues/52345
• vscode
• compiler (updated to current year)
• some repo with lots of ts-ignores
• vuelidate
• something with incremental parsing
• drizzle
• https://github.com/TryGhost/Ghost
• prisma something (https://github.com/microsoft/TypeScript/issues/44033#issuecomment-1698701239)
• new angular
• https://github.com/ChromeDevTools/devtools-frontend this build is way too custom; tsconfigs do not actually build
• https://github.com/growthbook/growthbook/blob/main/packages/back-end/tsconfig.json
• https://github.com/bluesky-social/social-app

Being in this list does not guarantee that actually want to add the benchmarks, or that there aren't other benchmarks we could add.

Our benchmarking system uses tuned physical machines for accurate measurement, so benchmarking time is limited. More capacity is on the way, and removing our old legacy internal benchmarks will free up more time.

Start with the benchmark criteria and the unchecked candidates listed in the issue, then inspect the existing benchmark structure for a comparable checked entry such as webpack or vscode. A contribution would need to select and integrate a candidate whose project compiles with the stated TypeScript commands in the target time; the issue does not name specific files or tests.