@danypops/vehicle-client
v0.5.1
Published
Vehicle clients: a same-process LocalVehicleClient (./local), an authenticated-HTTP RemoteVehicleClient (./http), plus the generic connection-resilience toolkit any client reaching a Vehicle server needs (retry-on-stale-connection, auto-spawn/fail-closed
Readme
@danypops/vehicle-client
Every way to reach a Vehicle server: a same-process LocalVehicleClient
(./local) and an authenticated-HTTP RemoteVehicleClient (./http), plus
the generic connection-resilience toolkit any client needs -- retry-on-stale-
connection, auto-spawn/fail-closed policy, version checking, push-channel
reconnection, and authenticated RPC over HTTP (./rpc-client) or a Unix
socket (./unix-rpc-client). No root export -- each subpath is a real,
independent capability; importing one must never pull in another it doesn't
need.
bun add @danypops/vehicle-client @danypops/vehicle-core./daemon-client and ./unix-rpc-client are shipped pre-compiled
specifically for Pi's jiti extension loader; ./rpc-client and ./version
ship as raw TypeScript.
See the workspace README for the full module table and Vehicle package layout.
