Complete full adoption of TS7 / tsgo

[lightwalker-eth]

Background info

• TS7 doesn't have a full release yet, but is generally mature already.
• To optimize build times an upgrade to TS7 was implemented with Replace tsc with tsgo for 47% faster type checking #1574
• PR 1574:
  • skipped transitioning ENSIndexer to TS7 because TS7 / Ponder aren't compatible with each other yet.
  • made use of a preview (non-final) release of TS7: "@typescript/native-preview": "7.0.0-dev.20260128.1"

Goals

1. Complete a full transition of all apps / packages across the ENSNode monorepo to TS7, including ENSIndexer.
2. Update the devDependencies in the root package.json file to switch to a full (non-preview) release of TS7 / tsgo once Microsoft makes a full TS7 release.

For investigation

1. Should we also update VSCode settings in .vscode/settings.json to make use of TS7 / tsgo? For example:

{
    "typescript.experimental.useTsgo": true
}

2. Do we still need to explicitly set rootDir in some of our tsconfig.json files? Maybe these explicit rootDir configs can be removed now? Needs verification. Background info: Assume rootDir is the current configuration directory microsoft/TypeScript#62194 was closed as part of the work on TS7.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#1516 - feat: new sepolia-v2 namespace for temp ensv2 deployment [merged]
#1560 - Deps/zod update [merged]
#1570 - deps: fix audit flags [merged]

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!