TypeScript 7 is the native Go compiler and removes `baseUrl` and `moduleResolution: node|node10`. Both appear here, so `tsc` from TS7 refuses the config outright (TS5102 / TS5108) and cannot typecheck. `paths` targets resolve relative to `baseUrl` when it is set and relative to the tsconfig file otherwise. Every `baseUrl` folded here already pointed at the config's own directory, so dropping it moves nothing and the targets are left byte-identical. Where a baseUrl pointed elsewhere, each affected target was rewritten as join(baseUrl, target). `moduleResolution` was chosen from the declared `module`: commonjs -> node16, esnext/preserve -> bundler. Configs whose `module` is unset or exotic were left alone rather than guessed at. The result is accepted by BOTH toolchains, so nothing has to upgrade TypeScript in lockstep. Verified on hanzo/chat packages/api: tsc 5.9 779 -> 778 errors (no regression), and tsc 7.0.2 now runs the project in 2s where it previously refused the config. Co-authored-by: Hanzo Dev <[email protected]>
19 lines
361 B
JSON
19 lines
361 B
JSON
{
|
|
"files": [],
|
|
"references": [
|
|
{ "path": "./tsconfig.app.json" },
|
|
{ "path": "./tsconfig.node.json" }
|
|
],
|
|
"compilerOptions": {
|
|
"paths": {
|
|
"@/*": ["./src/*"]
|
|
},
|
|
"noImplicitAny": false,
|
|
"noUnusedParameters": false,
|
|
"skipLibCheck": true,
|
|
"allowJs": true,
|
|
"noUnusedLocals": false,
|
|
"strictNullChecks": false
|
|
}
|
|
}
|