safe-global / safe-client-gateway / 37758861904

90%

push

github

build: move build and runtime to the native TypeScript 7 compiler (#3476)

CGW now builds and runs on `typescript@7.0.2`, the native Go compiler. Nest CLI (`nest build`/`nest start`) was compiling with its own bundled TypeScript 5.9.3; only CI's `yarn tsc --noEmit` ran on the 6.0.3 declared in `package.json`. TS 7 ships the `tsc` binary and no JS compiler API, so `@nestjs/cli`, `@nestjs/schematics`, `ts-node`, `ts-loader`, `tsconfig-paths` and `source-map-support` are removed together with `nest-cli.json`. `@swc/core` and `unplugin-swc` stay because Vitest still transforms specs through SWC.

TypeScript never rewrites `paths` aliases; Nest CLI was the component rewriting `@/` to relative paths in `dist` during emit. `yarn build` now runs `tsc-alias` after `tsc` to do the same rewrite, so `dist` stays self-contained and runs with plain `node dist/src/main.js` exactly as before. `tsc-alias` is a devDependency and never reaches the production image; no runtime code or flags change.

Yarn is bumped from 4.14.1 to 4.18.0 as a necessary consequence: the built-in `compat/typescript` patch in earlier Yarn releases fails on TS 7's package layout (`ENOENT lstat .../lib/_tsc.js`), which blocks installing `typescript@7` at all. 4.18.0 is the first release that handles it.

The scripts previously run through `ts-node` now run from `dist/scripts` after `yarn build` (the production image already did this for the KMS/token scripts), so `PROJECT_ROOT` in the env scripts is `process.cwd()` since a `__dirname`-relative path would point at `dist`. `start:dev`/`start:debug` run `tsc --watch`, `tsc-alias --watch` and `node --watch` through `concurrently` after an initial build.

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

4585 of 5377 branches covered (85.27%)

Branch coverage included in aggregate %.

11668 of 12782 relevant lines covered (91.28%)

549.25 hits per line