We deserve a better streams API for JavaScript
Handling data in streams is fundamental to how we build applications. To make streaming work everywhere, the WHATWG Streams Standard (informally known as "Web streams") was designed to establish a common API to work across browsers and servers. It shipped in browsers, was adopted by Cloudflare Workers, Node.js, Deno, and Bun, and became the foundation for APIs like fetch(). It's a significant unde
Reading and writing Node.js streams
Working with large datasets in Node.js applications can be a double-edged sword. The ability to handle massive amounts of data is extremely handy, but can also lead to performance bottlenecks and memory exhaustion. Traditionally, developers tackled this challenge by reading the entire dataset into memory at once. This approach, while intuitive for smaller datasets, becomes inefficient and resource
Web Streams Everywhere (and Fetch for Node.js) | CSS-Tricks
Get affordable and hassle-free WordPress hosting plans with Cloudways — start your free trial today. Chrome developer advocate Jake Archibald called 2016 “the year of web streams.†Clearly, his prediction was somewhat premature. The Streams Standard was announced back in 2014. It’s taken a while, but there’s now a consistent streaming API implemented in modern browsers (still waiting on Firefox…)
A Visual Guide to NodeJS Streams
Background Image Courtesy: Photo by Joshua Sortino on UnsplashImagine you have a pile of bricks somewhere. And you want to build a wall with those bricks here. Let’s say you have a friend to help move the bricks. To start building, you now have two options. You can either wait until your friend brings the whole pile of bricks to you, or you can start building as soon as you have a few bricks to st
Streams—The definitive guide  | Articles  | web.dev
The Streams API allows you to programmatically access streams of data received over the network or created by whatever means locally and process them with JavaScript. Streaming involves breaking down a resource that you want to receive, send, or transform into small chunks, and then processing these chunks bit by bit. While streaming is something browsers do anyway when receiving assets like HTML
GitHub - isaacs/minipass: A stream implementation that does more by doing less
A very minimal implementation of a PassThrough stream It's very fast for objects, strings, and buffers. Supports pipe()ing (including multi-pipe() and backpressure transmission), buffering data until either a data event handler or pipe() is added (so you don't lose the first chunk), and most other cases where PassThrough is a good idea. There is a read() method, but it's much more efficient to con
JavaScriptã®Streams APIã§ç´°åˆ‡ã‚Œã®ãƒ‡ãƒ¼ã‚¿ã‚’èªã¿æ›¸ãã™ã‚‹
è¿‘å¹´ã€PCã«æ載ã•ã‚Œã‚‹ãƒ¡ãƒ¢ãƒªã¯çˆ†ç™ºçš„ã«å¢—ãˆã¾ã—ãŸã€‚16GBã‚„32GBã®ãƒ¡ãƒ¢ãƒªãŒæ載ã•ã‚Œã¦ã„ã‚‹ã®ãŒå½“ãŸã‚Šå‰ã®æ™‚代ã§ã™ã€‚性能ã®åˆ¶é™ãŒå¼·ã„スマートフォンã§ã™ã‚‰4GBã»ã©æ載ã—ã¦ã„ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ストレージã®èªã¿æ›¸ã速度もã©ã‚“ã©ã‚“åŠ é€Ÿã—ã€æ˜”ã§ã¯æ‰±ãˆãªã‹ã£ãŸã‚ˆã†ãªãƒ‡ãƒ¼ã‚¿é‡ã‚’リアルタイムã§å‡¦ç†ã§ãã¾ã™ã€‚インターãƒãƒƒãƒˆå›žç·šã‚‚åŒæ§˜ã«å¤§é‡ã®ãƒ‡ãƒ¼ã‚¿ã‚’扱ãˆã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ ã—ã‹ã—ç¾å®Ÿçš„ãªå¤§ãã•ã®ãƒ‡ãƒ¼ã‚¿ã‚’一度ã«æ‰±ãŠã†ã¨ã™ã‚‹ã¨ã€ç¾ä»£ã§ã‚‚ãã‚Œãªã‚Šã«å‡¦ç†æ™‚é–“ãŒã‹ã‹ã‚Šã¾ã™ã€‚ユーザã¯ãƒ¬ã‚¹ãƒãƒ³ã‚¹ã«å¯¾ã—ã¦æ•æ„Ÿã§ã€åå¿œãŒ0.1秒ã§ã‚‚é…れるã¨ã‚¹ãƒˆãƒ¬ã‚¹ã‚’æ„Ÿã˜ã¾ã™ã€‚ã—ã‹ã—時間ãŒã‹ã‹ã‚‹ã‚‚ã®ã¯ã‹ã‹ã‚‹ã®ã§ã™ã€‚ã“ã®å•é¡Œã¯ä¸€è¦‹ã©ã†ã—よã†ã‚‚ãªã„よã†ã«æ€ãˆã¾ã™ã€‚ ãã“ã§ç™»å ´ã™ã‚‹ã®ãŒã€Œãƒ‡ãƒ¼ã‚¿ã‚’細切れã«ã—ã¦å‡¦ç†ã™ã‚‹ã€ã¨ã„ã†ã‚³ãƒ³ãƒ”ュータã«ãŠã‘る万能ã®è–¬ã§ã™ã€‚細切れã«ã—ã¦é€æ¬¡å‡¦ç†ã™ã‚Œã°ã€å°‘ã—ãšã¤ãƒ‡ãƒ¼ã‚¿ã‚’処ç†ã™ã‚‹ã“ã¨ãŒã§ãã€ç´ æ—©ã„レスãƒãƒ³ã‚¹ã‚’実ç¾ã™ã‚‹ã“
The WHATWG Blog — Progressing Streams
Please leave your sense of logic at the door, thanks! Progressing Streams July 5th, 2017 by Adam Rice in What's Next Back in 2014 we announced the Streams Standard. It's about time for an update on where we are and what's coming up. Streaming the response to fetch() via the response.body attribute was standardized last year and is now implemented in several major browsers. Recently streaming uploa
Node.js Streams: Everything you need to know
By Samer Buna Update: This article is now part of my book “Node.js Beyond The Basicsâ€. Read the updated version of this content and more about Node at jscomplete.com/node-beyond-basics. Node.js streams have a reputation for being hard to work with, and even harder to understand. Well I’ve got good news for you — that’s no longer the case. Over the years, developers created lots of packages out the
The Definitive Guide to Object Streams in Node.js - RisingStack Engineering
Node.jsNode.js is an asynchronous event-driven JavaScript runtime and is the most effective when building scalable network applications. Node.js is free of locks, so there's no chance to dead-lock any process. Streams come with a great power: You have an asynchronous way of dealing with input and output, and you can transform data in independent steps. In this tutorial, I’ll walk you through the t
streams/FAQ.md at main · whatwg/streams
This is a work in progress, documenting some design decisions that were made and that were non-obvious enough that we feel the need to explain them. We'll probably be adding to it as we go. If there's something you feel belongs here, please file an issue or pull request and we'll add it! Readable streams fit best in situations where: You are trying to represent some underlying I/O source of data,
Stream API入門 - Qiita
Nodeã®ã‚¢ãƒ‰ãƒ™ãƒ³ãƒˆã‚«ãƒ¬ãƒ³ãƒ€ãƒ¼ã€æ—¢ã«çµ‚ã‚ã£ãŸæž ãŒç©ºã„ã¦ã„ã¦ã€ã“ã®éš›æ›¸ããŸã„ãƒã‚¿ãŒã‚ã£ãŸã‚“ã§å‚åŠ ã—ã¾ã—ãŸã€‚宜ã—ããŠé¡˜ã„ã—ã¾ã™ã€‚ アドベントカレンダーã®æ™‚期ã ã‘出没ã™ã‚‹å¼±ã„日曜Haskellerã§ã™ã€‚普段ã®å®Ÿå‹™ã§ã¯Node.jsã«ãŠä¸–話ã«ãªã£ã¦ã¾ã™ã€‚宜ã—ããŠé¡˜ã„ã—ã¾ã™ã€‚ ã•ã¦ã€ã¿ãªã•ã‚“Stream API使ã£ã¦ã¾ã™ã‹ï¼ŸNode.jsã¨ã„ã£ãŸã‚‰éžåŒæœŸã§ã™ã‚ˆãã€ã‚„ã£ã±ã‚Šã€‚ã—ã‹ã—ãªãŒã‚‰ã€JavaScriptã§ã‚‚ä»–ã®è¨€èªžã§ã‚‚ã€éžåŒæœŸå‡¦ç†è‡ªä½“ã¯æ³¨ç›®ã•ã‚Œã¦ã„ã‚‹ã‚‚ã®ã®ã€ã¾ã experimentalã¨ã„ã†æ„Ÿã˜ã§æ§˜ã€…ãªAPIãŒè€ƒæ¡ˆã•ã‚Œã¦ã¯æ¶ˆãˆã¦ã„ãã€ã¾ãŸå…ƒã€…ãã†ã„ã†æ–‡åŒ–ãŒæ ¹å¼·ããªã‹ã£ãŸã¨ã“ã‚ã‹ã‚‰æ¥ãŸäººãŸã¡ã«ã¨ã£ã¦ã€ã“ã†ã„ã†æ–‡åŒ–ã¯ã¡ã‚‡ã£ã¨ç«‹ã¡å…¥ã‚Šã¥ã‚‰ã„ã¨ã“ã‚ã‚‚ã‚ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ã。 今日ã¯ã€ä¸»ã«ãã†ã„ã†äººãŸã¡ã«å‘ã‘ã¦ã€ã¾ãšéžåŒæœŸã®è‰²ã€…ãªAPIã®ç´¹ä»‹ã€ãã—ã¦ãã®ä¸ã§ã®ã‚¹ãƒˆãƒªãƒ¼ãƒ ã®ãƒ¡ãƒªãƒƒãƒˆã€ãã—ã¦å®Ÿéš›ã®Stream
メンテナンス
ランã‚ング
ãŠçŸ¥ã‚‰ã›
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Using web streams on Node.js
GitHub - MattiasBuelens/web-streams-polyfill: Web Streams, based on the WHATWG spec reference implementation
Chrome Platform Status
streams/transferable-streams-explainer.md at main · whatwg/streams
GitHub - push-stream/push-stream
GitHub - Fishrock123/bob: 🚰 binary data "streams+" via data producers, data consumers, and pull flow.
GitHub - dojo/streams: :rocket: Dojo 2 - WHATWG compliant streams.
The Definitive TypeScript Guide - Blog | SitePen
{{#tags}}- {{label}}
{{/tags}}