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 🙏

© 2026 – Pkg Stats / Ryan Hefner

mowr

v1.2.0

Published

A very thin convenience wrapper for the Mongo client.

Readme

Mowr 😺 makes using the Mongo client more comfy

npm GitHub file size in bytes
A very thin convenience wrapper for the Mongo client.

Installation

npm i mowr

Usage

const db = require('mowr')('localhost:27017/test', options)
const collection = db.get('collection')

const collection = require('mowr')('localhost/test', options).get('collection')

Supported calls

collection.find(query, options)    // returns array
collection.findc(query, options)   // returns cursor
collection.findOne(query, options) // returns object

collection.insert(object/array, options) // returns inserted object/array
collection.insertOne(object, options)    // returns inserted object
collection.insertMany(array, options)    // returns inserted array

collection.updateOne(query, update, options)  // -> {n: 1, nModified: 1, ok: 1}
collection.updateMany(query, update, options) // -> {n: 5, nModified: 5, ok: 1}
collection.replaceOne(query, update, options) // -> {n: 1, nModified: 1, ok: 1}

collection.deleteOne(query, options)  // -> {n: 1, ok: 1}
collection.deleteMany(query, options) // -> {n: 5, ok: 1}

collection.findOneAndUpdate(query, update, options)  // returns original document
collection.findOneAndReplace(query, update, options) // returns original document
collection.findOneAndDelete(query, options)          // returns deleted document

Options are always optional, and passed as object.

When connecting, 'mongodb://' is prepended if needed, and useUnifiedTopology is set to true (pass it as option to set it to false).

The query field can be an _id string (it will be converted to {_id: <ObjectID>}) or a query object.

Depending on if an object or array is passed in, insert will call insertOne or insertMany.

If an update object contains an _id property, even if nested, it will be removed.

When passing options using find, findc, findOne, make sure to use a query (can be {}).


Thanks to @fuzetsu for his invaluable help!