NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #2304 most downloaded on npm
Stringify JS values
Latest stable
1.8.0
Last release 13 days ago
09 Nov 2026
Release timing varies
gaps range from 9 days to 2 months
Some releases are documented
notes for 14 of 49 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
49 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
7fe0193: The web plugins check their fields with validate. A field with the wrong type now throws SerovalPluginValidationError, as the cause of the de
validate. A field with the wrong type now throws SerovalPluginValidationError, as the cause of the decoding error. The ReadableStream plugin now also checks that its source is a stream. seroval-plugins now needs seroval 1.8.0 or newer.seroval/shared instead of seroval, so a bundle that only reads or only writes does not pull in the other side through them.### Patch Changes - Harden decoding limits.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
bb4c3fc: Streamed Request payloads now deserialize where stream request bodies are supported. RequestPlugin adds duplex: 'half' to the request options
bb4c3fc: Streamed Request payloads now deserialize where stream request bodies are supported. RequestPlugin adds duplex: 'half' to the request options when the body is a ReadableStream, which Chrome 105+ and Node 19.1+ require. Runtimes without stream request bodies ignore the option.
RequestPlugin also keeps the body of a Request in runtimes without the Request.body getter, such as Firefox. The async parse reads the body with arrayBuffer(), and the stream parse pushes that buffer into a new ReadableStream.
eb60188: Check the File, ImageData, Event and CustomEvent fields during deserialization. The options of each are checked field by field and copied, an
Uint8ClampedArray.Check the FormData, Headers, Response and Request fields during deserialization.
Check that a ReadableStream's stream source is a seroval Stream before deserializing it.
No changes in this release.
No changes in this release.
Nothing published for this version
2d03651: serialize, toJSON, crossSerialize and toCrossJSON now throw when the value contains an async iterable or a ReadableStream, as they do for a p
serialize, toJSON, crossSerialize and toCrossJSON now throw when the value contains an async iterable or a ReadableStream, as they do for a promise. Before, they sent a stream that never got its values. Use an async or streaming function to send them.4c0008f: Add createLiveStream(), a single-consumer stream that holds one event at a time and resolves each producer write only after the serialized re
createLiveStream(), a single-consumer stream that holds one event at a time and resolves each producer write only after the serialized record is accepted. crossSerializeStream and toCrossJSONStream callbacks may now return a promise; the next record, and the acceptance of the source event behind it, wait for it to settle. Records discovered while parsing an event are emitted after the record that introduces them, one callback runs at a time, onDone waits for the last callback and is not called after an output failure, and cleanup runs every callback once. Async iterables and ReadableStream values read their next chunk only after the previous record is accepted. Existing streaming plugin lifecycle hooks remain available; parsing a live stream is the preferred way to connect an incremental source.>=10 to >=20 in engines, remove the no-op typesVersions from seroval, give seroval-plugins main, module and types fields plus a typesVersions entry that points at the emitted web declarations, and link the plugins package to the workspace copy of seroval.engines.node, keeping nullish coalescing and optional chaining as written.URL, Blob and Headers, now set skipPlainObjects. With a seroval version that supports it, serializing plain objects with these plugins is faster.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
fix: streaming serialization cleanup
Credits to @spokodev and @greymoth-jp
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Move AbortSignal to seroval-plugins/web
AbortSignal to seroval-plugins/web
AbortSignal is a web standard.onParse, pushPendingState, popPendingState and parseWithError in Plugin API.status and value is now replaced with s (0, 1, 2 as pending, success, failure) and v respectively.new Date(NaN) is a thing.Nothing published for this version
Add AbortSignal to serializable values
AbortSignal to serializable valuesNothing published for this version
This feature adds a very basic OpaqueReference class. The purpose of this class is to wrap user-specified values into "opaque references": references
This feature adds a very basic OpaqueReference class. The purpose of this class is to wrap user-specified values into "opaque references": references that are hidden from the serializer. An OpaqueReference contains two values: the original value it is trying to hide, and an optional replacement value, which is what the serializer "sees".
A replacement value can only be a value that seroval can serialize. By default, a replacement value is undefined.
Example:
import { serialize, deserialize, OpaqueReference } from 'seroval';
const example = {
transparent: "This is a transparent value.",
opaque: new OpaqueReference('This is an opaque value.'),
};
// You can still access the original value:
console.log(example.opaque.value);
// but now it's different
const deserialized = deserialize(serialize(example));
console.log(deserialized.opaque); // undefined
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Deprecate some feature flags. The following features can no longer be disabled:
createStream https://github.com/lxsmnsyc/seroval/pull/36/commits/a4039554433b785197572252afe24810067e75aa
ReadableStream isn't a JS standard and so there was no counterpart to Promise when it comes to streaming data, so I had to introduce a minimal streaming primitive that is both portable and serializable.seroval-plugins https://github.com/lxsmnsyc/seroval/pull/36/commits/22dcc59d2e165340809b81adaba8799a0049d7cc
createStream has been introduced, seroval is no longer dependent from the ReadableStream API, which makes seroval no longer tied to the Web API too.seroval-plugins/web
BlobCustomEventDOMExceptionEventFileFormDataHeadersReadableStreamRequestResponseURLSearchParamsURLSetMapPromiseBigIntTypedArraySymbolWebAPIPromise and AsyncIterable is now supported in sync mode, but will only generate a non-resolving instance.extends option to Plugins API. This allows the plugins to require other plugins in case the feature is required (e.g. Request relies on both Headers and ReadableStream)RegExp serializationFull Changelog: https://github.com/lxsmnsyc/seroval/compare/v0.15.1...v1.0.0
One column per month.