SubprocessConnectOptions
Defined in: src/client/types.ts:130
Options for subprocessConnect, which spawns a server process and pipes to it.
Extends
Section titled “Extends”Properties
Section titled “Properties”optional cwd?: string;Defined in: src/client/types.ts:132
Working directory for the spawned process. Defaults to the current directory.
optional env?: Record<string, string>;Defined in: src/client/types.ts:134
Extra environment variables, merged over the current process.env.
externalLocation?
Section titled “externalLocation?”optional externalLocation?: ExternalLocationConfig;Defined in: src/client/types.ts:96
External storage config for resolving externalized batches.
Inherited from
Section titled “Inherited from”PipeConnectOptions.externalLocation
onLog?
Section titled “onLog?”optional onLog?: (msg) => void;Defined in: src/client/types.ts:94
Callback invoked for each log/error message the server emits during a request.
Parameters
Section titled “Parameters”| Parameter | Type |
|---|---|
msg |
LogMessage |
Returns
Section titled “Returns”void
Inherited from
Section titled “Inherited from”protocol?
Section titled “protocol?”optional protocol?: string;Defined in: src/client/types.ts:92
Which protocol to bind to, skipping reflection’s list_protocols hop.
Introspection is two round trips – what does this server host, then describe one of them – because a server may host several and there is no longer a single “the” protocol to ask about without asking. Naming one here answers the first question locally. Defaults to the first hosted protocol that is not framework-reserved.
Inherited from
Section titled “Inherited from”stderr?
Section titled “stderr?”optional stderr?: "inherit" | "pipe" | "ignore";Defined in: src/client/types.ts:136
How to handle the child’s stderr. Defaults to "ignore".