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

digger-mongo

v0.1.1

Published

Mongo supplier for digger

Downloads

71

Readme

digger-mongo

Mongo supplier for digger

installation

$ npm install digger-mongo

usage

This library allows you to save digger databases into MongoDB.

var Mongo = require('digger-mongo');

// create the supplier
var supplier = Mongo({
	hostname:'127.0.0.1',
  port:27017,
  database:'mydb',
  collection:'mycollection',
  reset:false,
  nocache:false
})

// run a request against the supplier
supplier({
	method:'get',
	url:'/selector'
}, function(error, answer){
	console.log('-------------------------------------------');
	console.log('we have loaded the selector via REST');
})

provisioning

Sometimes it is useful for a supplier to provision the database and/or collection depending upon the url of the request.

For example - imagine I mounted a Mongo supplier onto:

/mymongosupplier

If I configure it with a specific database and collection then there is no provisioning required - because I have statically assigned what database and collection.

However - if I only configure the database property and leave the collection for provisioning - it will use the url of the request to decide what collection to use:

var supplier = Mongo({
	database:'mydb',
	provision:['collection']
})

supplier({
	method:'get',
	url:'/database_mount/db1234'
}, function(error, result){

})	

This allocates db1234 as the collection name

licence

MIT