Wondering what’s next for npm?Check out our public roadmap! »

    TypeScript icon, indicating that this package has built-in type declarations

    3.0.3 • Public • Published


    SOFT DEPRECATION: Please use native Readable async iteration support instead, available from node.js v10.

    Converts a node.js stream into an iterator.

    Build Status Dependency Status devDependency Status node


    With for-await-of:

    (async () => {
      const streamToIterator = require('stream-to-iterator')
      const intoStream = require('into-stream')
      const readable = intoStream.obj([2, 3, 4])
      const iterator = streamToIterator(readable)
      const allValues = []
      for await (let value of iterator) {
        allValues.push(value * value)
      console.log(allValues) // [ 4, 9, 16 ]


    streamToIterator(readable, opts)

    Creates a writable stream that is also an async iterator and pipes the readable stream to it. Chunks are drained from the source stream as objects are requested from the iterator.

    Requested values are fulfilled serially. Requesting a value (AsyncIterator#next) from the iterator without waiting for a previous request to finish will result to the resolved value being equal to the resolved value of the previous request.

    The underlying writable stream defaults to object mode. This is because the object converted into (the iterator) does not really need to be in a specific object or non-object mode.

    For convenience, the iterator also implements the AsyncIterable interface. Be careful though: this only reflects the current state of the iterator.

    The iterator will rethrow any error emitted on the stream on the next iteration read from it after the error is handled.


    • readable: Readable<T> - A node.js-style readable stream. Streams v1-3 are supported (via node core Readable.wrap()).
    • opts: Object - Options to pass to the underlying writable stream. Default: { objectMode: true }. No merging is performed.

    Returns: AsyncIterator<T> where AsyncIterator<T> is:

    interface AsyncIterator<T> {
      next(): Promise<{ done: boolean; value: T }>

    Migrating from v2

    The old mode implementing Iterator<Promise<T>> is still supported. However, there are a few breaking changes:

    • streamToIterator does not return a Promise anymore.
    • To get an instance of the iterator, call [Symbol.iterator]() on the return value.
    • Call await init() on the returned iterator to initialize it. This is the equivalent of calling the removed Promise interface on the original function.
    • As with the new API, calling Iterator#next before waiting for the promise to finish will return the same value as the previous iteration.
    const iterator = await streamToIterator(readable).init()
    for (let valuePromise of iterator) {
      const value = await valuePromise
      // do something with value

    (See also the example on the tests.)

    The old consumption rules still apply:

    • The iteration value returned will be of type Promise<T>. To get the iteration value, the consumer must wait for the resolution of that promised value.
    • The consumer must not prematurely get the next value of the iterator (i.e. call Iterator#next()) until such time that the current promise value of the iterator is resolved.

    The iterator throws if the iterator was called before the first chunk was received.

    See also


    npm i stream-to-iterator

    DownloadsWeekly Downloads






    Unpacked Size

    28.1 kB

    Total Files


    Last publish


    • avatar