npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

promise-transform-streams

v1.0.0

Published

Create and resolve a promise of streams

Downloads

5

Readme

promise-transform-streams

NPM version Build status Test coverage Dependency Status License Downloads Gittip

Creates promise-based transform streams. .map() creates a stream that converts objects to promises. .resolve() resolves all these promises.

The main use-case for this is to create "concurrent" transform that preserve order. This module does not apply any concurrent limits! However, you could play with the buffer sizes, which indirectly relate to concurrency in this context.

Example

Suppose you have MongoDB documents that look like this:

var post = {
  creator_id: ObjectId('123412341234123412341234'),
  title: 'some title',
  markdown: 'blah'
}

You want to grab all the .creators, but you still want to stream all the results. Here's how to do it:

var PStream = require('promise-transform-stream')

db.posts.find({}).stream()
// get the creator of each post, returns a stream of promises
.pipe(PStream.map(getCreator))
// resolves each promise in the stream in order
.pipe(PStream.resolve())
// no we can serialize the results and send it to the client!
.pipe(JSONStream.stringify())
.pipe(zlib.createGzip())
.pipe(res)

function getCreator(post) {
  return new Promise(function (resolve, reject) {
    db.users.findOne({
      _id: post.creator_id
    }, function (err, user) {
      if (err) return reject(err)
      post.creator = user
      resolve(post)
    })
  })
}

To be more efficient, you'd probably want to query each creator_id once per request.

API

.create(transform, [flush])

Create a new Transform constructor with ._transform and ._flush methods. transform should resolve to the mapped document. flush should not have any arguments.

var Transform = PStream.create(function (doc) {
  return Promise.resolve(doc)
})

db.posts.find({}).stream()
.pipe(Transform())

.map(transform, [flush])

The same as .create(), except it returns the transform instance immediately, through2-style. This is not recommended!

.resolve([options])

Returns a resolving transform stream.