Files
ui/pkg/hanzo/tsconfig.json
zeekayandHanzo Dev fc3463d89c Derive the hanzo exports map from its members
@hanzo/ui publishes 43 subpaths and adds more than anyone remembers to
mirror, so a hand-listed map rots into ERR_PACKAGE_PATH_NOT_EXPORTED under
a name that promised the subpath. scripts/gen.mjs reads the members' own
exports and writes one forwarder per subpath, by the member's specifier,
so the inner resolution happens in the consumer's node_modules under the
consumer's conditions and a forwarder cannot answer differently from what
it forwards to. 359 subpaths, and the suite asserts the map on disk still
says what the members say.

@hanzo/iam, @hanzo/ai and @hanzo/event join @hanzo/ui and @hanzo/gui as
members. src/ui.ts and src/gui.ts go: the generated forwarders are what
they were written by hand to be.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-08 15:04:30 -07:00

28 lines
1.0 KiB
JSON

{
"compilerOptions": {
"target": "ES2022",
"lib": ["ES2022", "DOM", "DOM.Iterable"],
"module": "ESNext",
"moduleResolution": "Bundler",
"jsx": "react-jsx",
"strict": true,
"allowJs": true,
"noEmit": true,
"isolatedModules": true,
"esModuleInterop": true,
"skipLibCheck": true,
"resolveJsonModule": true,
"forceConsistentCasingInFileNames": true,
"types": ["react", "node"],
// The suite loads the real @hanzo/ui and @hanzo/gui, and node cannot parse
// react-native's entry — it is Flow. So devDependencies put react-native-web
// under the name `react-native`, the substitution every web bundler makes.
// The web build ships no declarations and @hanzogui's sources are written
// against react-native's, so tsc reads those from the same package under a
// second name. Runtime and types then each get the one that is right for it.
"paths": { "react-native": ["./node_modules/react-native-types"] }
},
"include": ["src"],
"exclude": ["node_modules", "dist", "dist-cjs"]
}