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

express-mongo-logger

v1.0.5

Published

A different logger for express, that uses mongodb

Readme

MongoLogger

MongoLogger was created after an immense amount of frustration using Winston to log requests and errors to MongoDB. Nothing was formatted the way I wanted it to be so I created MongoLogger.

Example Log

An example of a logged document with all features enabled can be found here

Getting Started

Run npm i express-mongo-logger

var mongoLogger = require("express-mongo-logger");
var express = require("express");
var app = express();

app.use(
	mongoLogger({
		mongoConnectionString: "mongodb://<User>:<Password>@<Host>:<Port>/><Database>"
	})
);

app.get("/", async function (req, res, next) {
	res.send(`Hello World!`);
});

app.get("/404", async function (req, res, next) {
	res.status(404).send(`The requested resource cannot be found!`);
});

By default all requests will be logged. It is highly recommended to define minStatusCode:400 to only log errors.

Configuration Parameters

{
    mongoConnectionString: null, //MongoDB connection String
    minStatusCode: 200, //Minimum statuscode to log
    excludeHeadersParams: ["Authorization"], //Headers to remove in logs
    excludeBodyParams: null, //Body parameters to avoid logging (you should include all password fields at a minimum)
    excludeRouteParams: null, //Route parameters to avoid logging
    excludeQueryParams: null, //Query parameters to avoid logging
    exludeRequestTypes: ["OPTIONS"], //HTTP methods to not log
    includeFullRequest: true, //Include the full request object in log
    includeFullResponse: true, //Include the full response object in log
    extraTopLevelPropsRequest: [], //Add properties from req to the root of the document
    extraTopLevelPropsResponse: [], //Add properties from res to the root of the document
    normalCollection: "Log", //Collection to store all log events
    errorCollection: "ErrorLog", //Collection to store errors
    requestTime: true, // Log request time
    requestTime_nanoSeconds: false, //Use nanoseconds for requesttime instead of miliseconds
    returnError: true, // Send 500 status and response to client
}