@smithy/eventstream-serde-node
Advanced tools
The 'event-stream' package provides a toolkit for working with streams in Node.js. It includes utilities for creating, manipulating, and consuming streams. While it is more general-purpose compared to @smithy/eventstream-serde-node, it can be used to handle event streams in a similar manner.
The 'stream-json' package is designed for processing JSON streams in Node.js. It provides tools for parsing and stringifying JSON data in a streaming fashion. Although it is focused on JSON, it offers similar functionality for handling streaming data as @smithy/eventstream-serde-node.
The 'node-eventstore-client' package is a client for EventStore, a database optimized for event sourcing. It provides APIs for reading and writing event streams to an EventStore database. This package is more specialized compared to @smithy/eventstream-serde-node, focusing on integration with EventStore.
FAQs
Unknown package
The npm package @smithy/eventstream-serde-node receives a total of 21,579,739 weekly downloads. As such, @smithy/eventstream-serde-node popularity was classified as popular.
We found that @smithy/eventstream-serde-node demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
A mini Shai-Hulud campaign compromised Red Hat Cloud Services npm packages to steal developer and CI/CD secrets during installation.
Research
/Security News
The North Korean malware loader hides in a Packagist-listed package and its GitHub branch to fetch and execute remote code in a likely Contagious Interview-style lure.
Security News
The Rust project is moving toward formal rules on LLM use in contributions after months of internal debate over maintainer burden, code quality, and contributor experience.
