delayed-stream

中文文档
1.0.0发布于 2015/05/01MITCommonJS零依赖近 30 天下载 5.6亿

Buffers events from a stream until you are ready to handle them.

原始使用文档
文档目录18 节
  1. Installation
  2. Usage
  3. Implementation
  4. Event Buffering / Proxying
  5. Error handling
  6. Buffer limits
  7. API
  8. DelayedStream.create(source, [options])
  9. delayedStream.source
  10. delayedStream.pauseStream = true
  11. delayedStream.maxDataSize = 1024 * 1024
  12. delayedStream.dataSize = 0
  13. delayedStream.readable
  14. delayedStream.resume()
  15. delayedStream.pause()
  16. delayedStream.pipe(dest)
  17. delayedStream.release()
  18. License

delayed-stream

Buffers events from a stream until you are ready to handle them.

Installation

npm install delayed-stream

Usage

The following example shows how to write a http echo server that delays its response by 1000 ms.

var DelayedStream = require('delayed-stream');
var http = require('http');

http.createServer(function(req, res) {
  var delayed = DelayedStream.create(req);

  setTimeout(function() {
    res.writeHead(200);
    delayed.pipe(res);
  }, 1000);
});

If you are not using Stream#pipe, you can also manually release the buffered events by calling delayedStream.resume():

var delayed = DelayedStream.create(req);

setTimeout(function() {
  // Emit all buffered events and resume underlaying source
  delayed.resume();
}, 1000);

Implementation

In order to use this meta stream properly, here are a few things you should know about the implementation.

Event Buffering / Proxying

All events of the source stream are hijacked by overwriting the source.emit method. Until node implements a catch-all event listener, this is the only way.

However, delayed-stream still continues to emit all events it captures on the source, regardless of whether you have released the delayed stream yet or not.

Upon creation, delayed-stream captures all source events and stores them in an internal event buffer. Once delayedStream.release() is called, all buffered events are emitted on the delayedStream, and the event buffer is cleared. After that, delayed-stream merely acts as a proxy for the underlaying source.

Error handling

Error events on source are buffered / proxied just like any other events. However, delayedStream.create attaches a no-op 'error' listener to the source. This way you only have to handle errors on the delayedStream object, rather than in two places.

Buffer limits

delayed-stream provides a maxDataSize property that can be used to limit the amount of data being buffered. In order to protect you from bad source streams that don't react to source.pause(), this feature is enabled by default.

API

DelayedStream.create(source, [options])

Returns a new delayedStream. Available options are:

  • pauseStream
  • maxDataSize

The description for those properties can be found below.

delayedStream.source

The source stream managed by this object. This is useful if you are passing your delayedStream around, and you still want to access properties on the source object.

delayedStream.pauseStream = true

Whether to pause the underlaying source when calling DelayedStream.create(). Modifying this property afterwards has no effect.

delayedStream.maxDataSize = 1024 * 1024

The amount of data to buffer before emitting an error.

If the underlaying source is emitting Buffer objects, the maxDataSize refers to bytes.

If the underlaying source is emitting JavaScript strings, the size refers to characters.

If you know what you are doing, you can set this property to Infinity to disable this feature. You can also modify this property during runtime.

delayedStream.dataSize = 0

The amount of data buffered so far.

delayedStream.readable

An ECMA5 getter that returns the value of source.readable.

delayedStream.resume()

If the delayedStream has not been released so far, delayedStream.release() is called.

In either case, source.resume() is called.

delayedStream.pause()

Calls source.pause().

delayedStream.pipe(dest)

Calls delayedStream.resume() and then proxies the arguments to source.pipe.

delayedStream.release()

Emits and clears all events that have been buffered up so far. This does not resume the underlaying source, use delayedStream.resume() instead.

License

delayed-stream is licensed under the MIT license.

版本与发布记录

delayed-stream 共发布 9 个版本,首次发布于 2011/05/22;过去 12 个月发布了 0 个版本。

版本发布日期距今
1.0.0latest2015/05/0111 年前
0.0.72015/05/0111 年前
0.0.62014/11/2311 年前
0.0.52011/05/2415 年前
0.0.42011/05/2415 年前
0.0.32011/05/2315 年前

关于 delayed-stream 的常见问题

delayed-stream 是什么?

Buffers events from a stream until you are ready to handle them.

如何安装 delayed-stream?

在项目目录运行 npm install delayed-stream,或使用 pnpm add / yarn add / bun add。

delayed-stream 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/delayed-stream 是否存在。

delayed-stream 支持 ESM 还是 CommonJS?

以 CommonJS 形式发布,可以直接 require();在 ES Module 项目中也可以用 import 引入(Node.js 会把 module.exports 作为默认导出)。

delayed-stream 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=0.4.0。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

delayed-stream 可以商用吗?

delayed-stream 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

delayed-stream 的下载量有多少?

根据 npm 官方下载统计,delayed-stream 在 2026/10/07 – 2026/11/05 这 30 天内被下载 556,986,221 次,日均约 18,566,207 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

delayed-stream 还在维护吗?

最新版本 1.0.0 发布于 2015/05/01(11 年前);至今共发布 9 个版本,其中过去 12 个月发布了 0 个;首次发布于 2011/05/22。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。