feat(bunfig): add toggle to disable tsconfig features

[DonIsaac]

What does this PR do?

• Documentation or TypeScript types (it's okay to leave the rest blank in this case)
• Code changes

How did you verify your code works?

[robobun]

^{Updated 8:46 PM PT - Jan 28th, 2025}

❌ @DonIsaac, your commit c57ef78 has 1 failures in Build #10739:

• test/js/bun/util/filesink.test.ts - timeout on 🪟 2019 x64
• test/js/bun/util/filesink.test.ts - timeout on 🪟 2019 x64-baseline

---

🧪   try this PR locally:

bunx bun-pr 16825

[DonIsaac]

• feat(bunfig): add toggle to disable tsconfig features  #16825 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Jarred-Sumner]

To serialize IRL discussion:

• tsconfig.json probably should be overriding package.json "exports" because that's what its meant for - giving people a way to override module resolution (curious if @andrewbranch has an opinion)
• The motivating usecase, Playwright's repo with a build step that relies on tsconfig.json paths at build-time and not being evaluated at runtime, is something we can support through the node shim we automatically use in bun --bun and through a bunfig.toml option to disable reading tsconfig.json

[andrewbranch]

tsconfig.json paths does indeed take precedence over everything else in TypeScript’s resolution, if that’s what you’re asking?