npm / @effect/platform
@effect/platform
What changed in @effect/platform 0.97, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-01.
3 breaking1 security1 new APIs and options10 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@effect/platform 0.9715 changes
Breaking changes 3
Passes the HttpServerResponse returned by the send handler to middleware instead of the handler's response.
Rejects invalid cookie names and cookie attribute separators in domains and paths.
File-backed key-value stores now reject empty,
.and..keys.
Security 1
Fixes a security issue in HTML escaping for generated Scalar and Swagger API documentation.
New APIs and options 1
Adds an extendEnv option for spawning commands with a clean environment.
Fixes and other changes 10
BunHttpServer logs status 101 for upgraded WebSocket requests.
Avoids throwing when Error.stackTraceLimit is non-writable, including in frozen-intrinsics, SES, and deterministic sandbox environments.
Keeps HTTP message bodies unread during inspection.
Preserves annotations on Union and multi-value Literal schemas, and prevents a Union response status set on one endpoint from leaking to other endpoints reusing the schema.
Decodes request bodies with a +json content type, such as application/scim+json, as JSON instead of raw bytes.
Builds the layer eagerly, preventing an aborted first request from leaving the handler hanging on runtimes such as Cloudflare workerd.
Fixes the @effect/platform-node implementation to return an ArrayBuffer instead of a Uint8Array.
Correctly parses raw UTF-8 filenames containing characters above U+00FF, which were previously parsed as fields with empty names.
Flattens the emitted anyOf for setPayload unions whose members share a content type.
Multipart limit failures are no longer silently ignored.