mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
zeekayandHanzo Dev
0a32777642
The client's source imported @hanzoteam/types, the name the sibling is PUBLISHED under, so that the emitted declarations would name what a consumer installs. But that package does not exist inside this monorepo — the workspace is @mattermost/ types — and tsconfig `paths` hid it: paths satisfy the type checker and change nothing tsc emits, so the 11 value imports among the 71 compiled into requires for a module no workspace provides. Type checking was green and the web app could not be bundled at all: "Can't resolve '@hanzoteam/types/client4'". So the rename moves to publish.mjs, which is where the other two renames already live and which is the only place that knows the published name is in play. The same OURS map is now read a third time, over the staged build output, matching a module specifier rather than a substring — @mattermost/typesNOTAPACKAGE is left alone. One name in the tree, one rename at the boundary, and the published .d.ts still names @hanzoteam/types so its types do not degrade to `any`. The image's Go stage moves to 1.26.6 because go.work now asks for >= 1.26.5 and the builder runs GOTOOLCHAIN=local, which does not fetch one: the base image has to carry it or the build stops before compiling anything. Co-authored-by: Hanzo Dev <[email protected]>
26 lines
602 B
JSON
26 lines
602 B
JSON
{
|
|
"compilerOptions": {
|
|
"module": "commonjs",
|
|
"moduleResolution": "node",
|
|
"target": "es2022",
|
|
"declaration": true,
|
|
"strict": true,
|
|
"skipLibCheck": true,
|
|
"resolveJsonModule": true,
|
|
"isolatedModules": true,
|
|
"esModuleInterop": true,
|
|
"allowSyntheticDefaultImports": true,
|
|
"jsx": "react",
|
|
"preserveConstEnums": true,
|
|
"outDir": "./lib",
|
|
"rootDir": "./src",
|
|
"composite": true,
|
|
},
|
|
"include": [
|
|
"./src/**/*"
|
|
],
|
|
"references": [
|
|
{"path": "../types"}
|
|
]
|
|
}
|