[dinwwwh]

Follows middleapi/orpc#2428: a feature is configured by one option that takes true/false or an object, so it can gain settings later without another rename. Also tidies option typing and renames a few unclear exports.

Breaking changes

Event stream options (fetch, node, and every adapter's eventStream option)

Before	After (default true)
initialComment: { enabled?, comment? }	initialComment?: boolean | { comment? }
keepAlive: { enabled, interval?, comment? }	keepAlive?: boolean | { interval?, comment? }

// before
toFetchResponse(res, { eventStream: { keepAlive: { enabled: false } } })
// after
toFetchResponse(res, { eventStream: { keepAlive: false } })

The object shapes are exported as ToEventStreamInitialCommentOptions and ToEventStreamKeepAliveOptions (also re-exported from @standard-server/node).

Renamed exports

Removed	Use instead	Why
ErrorEvent, ErrorEventOptions (core)	EventStreamErrorEvent, EventStreamErrorEventOptions	ErrorEvent shadows the global ErrorEvent; a missing import silently type-checks against the global and instanceof stops matching
assertEventStreamMessageName (core)	assertEventStreamMessageEvent	named after the event field it checks, like its Id / Retry / Comment siblings
canWriteToNodeResponse (node)	canWriteNodeHttpResponse	matches NodeHttpResponse, toNodeHttpBody
getNodeResponseError (node)	getNodeHttpResponseError	same
isNodeResponseDisconnectError (node)	isNodeHttpResponseDisconnectError	same
isTypescriptObject (shared)	isNonPrimitive	says what it checks: a non-null object or a function

Non-breaking

• Optional option properties now include | undefined, so callers using exactOptionalPropertyTypes can forward a possibly undefined value: eventStream, peer codec prefix, getOrBind's bind, EventStreamErrorEvent's message.
• fetch toStandardBody defaults options to {} like the other adapters; redundant options?. chaining removed.

Downstream

oRPC needs updates when it bumps standard-server: the initialComment / keepAlive examples in its handler, link, adapter and Nest docs and from-v1.mdx, packages/client/src/adapters/fetch/rpc-link.test.ts, and its uses of ErrorEvent and isTypescriptObject.

Testing

pnpm format, pnpm check, tsc and pnpm test (1486 tests) pass. Added a test that true enables the default initial comment and keep-alive.

---

Generated by Claude Code

[pkg-pr-new]

• @standard-server/hono-node-playground
• @standard-server/node-http-playground

@standard-server/aws-lambda

npm i https://pkg.pr.new/@standard-server/aws-lambda@185

@standard-server/core

npm i https://pkg.pr.new/@standard-server/core@185

@standard-server/fastify

npm i https://pkg.pr.new/@standard-server/fastify@185

@standard-server/fetch

npm i https://pkg.pr.new/@standard-server/fetch@185

@standard-server/node

npm i https://pkg.pr.new/@standard-server/node@185

@standard-server/peer

npm i https://pkg.pr.new/@standard-server/peer@185

@standard-server/shared

npm i https://pkg.pr.new/@standard-server/shared@185

commit: 1488668

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[codspeed]

Merging this PR will not alter performance

1 warning

⚠️ 4 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 26 untouched benchmarks
⏩ 108 skipped benchmarks¹

---

_{Comparing claude/sharp-brahmagupta-ekvj5s (1488668) with main (a382274)}

Footnotes

1. 108 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[pullfrog]

✅ No new issues found.

Reviewed changes

• Boolean-or-object event-stream options — initialComment and keepAlive in packages/fetch/src/event-stream.ts now accept boolean | <ObjectOptions> | undefined, with the object shapes exported as ToEventStreamInitialCommentOptions / ToEventStreamKeepAliveOptions and re-exported from @standard-server/node. Defaults are unchanged and coercion (!== false to disable) is consistent across both options.
• EventStreamErrorEvent rename — the core class and options interface no longer shadow the DOM global ErrorEvent; all core, fetch, peer, adapter, and e2e call sites were updated, and the intermediate deprecated aliases were removed before shipping.
• Node HTTP response helper renames — canWriteNodeHttpResponse, getNodeHttpResponseError, isNodeHttpResponseDisconnectError, plus the matching internal error-code set, with fastify / aws-lambda call sites updated.
• isNonPrimitive rename — isTypescriptObject renamed in @standard-server/shared, with validators, event-stream meta, and peer call sites updated.
• Optional-property | undefined — fetch/node eventStream, peer codec prefix, getOrBind's bind, and EventStreamErrorEventOptions.message, for exactOptionalPropertyTypes callers.
• fetch toStandardBody default — options: ToStandardBodyOptions = {}, dropping the redundant options?. chaining.
• Docs — core README examples and export list updated to the new names.

I also verified the rename is complete: a repo-wide search finds no remaining references to any removed identifier in source, tests, benches, playgrounds, or markdown, and pnpm check plus the full vitest suite (1486 tests) pass locally.

  ^{｜ View workflow run ｜ Using deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) ｜ 𝕏}