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 🙏

© 2025 – Pkg Stats / Ryan Hefner

mongodb-query-after

v0.0.6

Published

Add an after parameter to your queries

Downloads

13

Readme

MongoDB Query After Build Status

after support for queries instead of pagination. This ticket has been filed in jira.mongodb.org as a feature as this would be better if done on the database instead of the client.

You should only use this if after is actually used, otherwise just use a regular query.

API

query()

var query = require('mongodb-query-after')

query(collection, criteria, options).toArray()

These are the same arguments as collection.find(). Currently, all fields are required. The only difference is that there are two additional parameters for options:

  • options.after - Begins returning documents after the document with {_id: after}.
  • options.seek - Begins searching from the top of the query. Will stop the query after seek documents have been searched, regardless whether limit documents have been returned.

query().stream()

Returns a stream with only three events:

  • stream.on('error', function (err) {})
  • stream.on('end', function () {}), also aliased as close for ubiquity
  • stream.on('data', function (doc) {})

query().toArray(function (err, docs))

Equivalent to collection.find().toArray()

query().each(function (err, doc))

Equivalent to collection.find().each()