imccyu
027cbdfe5d
The Gateway and the carrier each compiled both halves under one tsconfig, so the Host aggregate built their browser faces — including the face that owns `ctx.remote`, the most likely future consumer of a generated `/remote` contribution. Both packages now expose a host and a client face, and each aggregate references only its own; three modules the halves share appear in both file lists, as api/remotes already does. The two apps/web specs in the Host aggregate restate the conversation engine's Context key format instead of importing the Client runtime for it. A drift makes the key miss its rendered node, so the assertion fails loudly. The Host aggregate now reaches one Client project, the carrier's host face, which the Gateway's own dispatch face needs; no generated contribution is reachable from it.
34 lines
659 B
JSON
34 lines
659 B
JSON
{
|
|
"extends": "../../../tsconfig.base.json",
|
|
"compilerOptions": {
|
|
"rootDir": "src",
|
|
"outDir": "lib/types",
|
|
"tsBuildInfoFile": "lib/tsconfig.host.tsbuildinfo"
|
|
},
|
|
"files": [
|
|
"src/api-path.ts",
|
|
"src/api-request-trust.ts",
|
|
"src/http-bridge.ts",
|
|
"src/index.ts",
|
|
"src/invariant.ts",
|
|
"src/loopback-hostname.ts",
|
|
"src/rpc-host.ts",
|
|
"src/rpc.ts",
|
|
"src/websocket-downlink.ts"
|
|
],
|
|
"references": [
|
|
{
|
|
"path": "../../attachment/attachment"
|
|
},
|
|
{
|
|
"path": "../../host/apiproxy"
|
|
},
|
|
{
|
|
"path": "../../host/webserver"
|
|
},
|
|
{
|
|
"path": "../../support/invariants"
|
|
}
|
|
]
|
|
}
|