Releases · ProjectOpenSea/stream-js

01 Jun 21:29

ryanio

v0.4.0

57e1905

v0.4.0 Latest

Latest

What's Changed

Add server-side event type filtering support. The onEvents method now passes an event_types array in the Phoenix channel join params, enabling the backend to filter events at subscription time. Individual on* methods remain backward-compatible (no event_types param — the server sends all events). (#375)

This is the SDK counterpart to the backend support for subscription-time event filtering.

Full Changelog: v0.3.1...v0.4.0

Assets 2

24 Apr 20:12

ryanio

v0.3.1

28e949a

v0.3.1

What's Changed

Migrate default WebSocket endpoint from wss://stream.openseabeta.com/socket to wss://stream-api.opensea.io/socket. The new endpoint connects to the Kotlin stream API service which reads directly from Kafka, reducing event delivery latency. No protocol or API changes — existing client code works without modification. (#113)

Full Changelog: ProjectOpenSea/opensea-devtools@stream-v0.3.0...stream-v0.3.1

Assets 2

17 Apr 19:21

ryanio

v0.3.0

1b33054

v0.3.0

Minor changes

Add version field to BaseStreamMessage for out-of-order event resolution (#70, OS2-31317)

Every stream event now includes a numeric version field that is monotonically increasing per source entity. Use it to handle out-of-order event delivery: when two events arrive for the same entity, the one with the higher version is newer state.

Version scale depends on event type

Event types	`version` semantic
`item_listed`, `item_cancelled`, `item_received_offer`, `item_received_bid`, `collection_offer`, `trait_offer`, `order_invalidate`, `order_revalidate`	Order revision counter (small monotonic integer per order)
`item_transferred`, `item_sold`, `item_metadata_updated`	Epoch milliseconds of the event's source timestamp

Both representations are monotonic and sufficient for resolving out-of-order delivery, but the two scales are not comparable to each other. Compare version only for the same entity within the same event family. See the Event Versioning section of the README for usage examples.

Notes

This is an additive change: BaseStreamMessage<Payload> gains a required version: number field.
No code changes required for existing consumers — events previously continued to work without the field at runtime; upgrading picks up the new typed field for those who want to use it.

Assets 2