mirror of https://github.com/getpaseo/paseo.git synced 2026-10-23 17:52:49 +00:00

Files

T

babo-jeongukandClaude Opus 5.5 df82edd218 Split the inbound WebSocket validator per message type (#6847 )

* Split the inbound WebSocket validator per message type

zod-aot compiled WSOutboundMessageSchema into one 11 MB function. Every
inbound frame, heartbeats included, ran through it, so V8 hosts (daemon
clients, plugin hosts, the CLI, Electron) eventually Maglev-compiled the
whole function: about 800 MB of compiler memory and multi-second stalls,
again after each deoptimization.

Generate a tag-only envelope validator plus one validator per session
message, and dispatch on the message type. Issue paths, defaults and
passthrough behave as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Use forward slashes in generated validator imports

path.relative() returns backslash paths on Windows, which break the
import specifiers written into the generated files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Declare the session export helper as a function

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-16 19:08:03 +02:00

codegen

Split the inbound WebSocket validator per message type (#6847 )

2026-10-16 19:08:03 +02:00

scripts

Split the inbound WebSocket validator per message type (#6847 )

2026-10-16 19:08:03 +02:00

src

Split the inbound WebSocket validator per message type (#6847 )

2026-10-16 19:08:03 +02:00

tests

Split the inbound WebSocket validator per message type (#6847 )

2026-10-16 19:08:03 +02:00

package.json

fix(ios): address clipped chat and Markdown text (#6445 )

2026-10-09 16:35:43 +01:00

README.md

Extract client SDK package (#1052 )

2026-05-28 01:58:18 +08:00

tsconfig.json

Extract client SDK package (#1052 )

2026-05-28 01:58:18 +08:00

README.md

@getpaseo/protocol

Shared Paseo protocol schemas, codecs, and wire types.

Stability

This package is public so Paseo's published packages can depend on it cleanly. It is not a stable public API yet.

Schemas, exports, wire helpers, and types may change or disappear in any release without advance notice. Use it outside Paseo at your own risk until the package is explicitly documented as stable.