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

@trace-dev/plugin-mongoose

v0.1.0

Published

trace-dev instrumentation for mongoose (MongoDB).

Readme

@trace-dev/plugin-mongoose

trace-dev instrumentation for mongoose (MongoDB). Installed automatically as part of @trace-dev/core — you only need this package directly if you want it without the rest of the bundle.

npm install @trace-dev/plugin-mongoose
import "@trace-dev/core/init";

With mongoose installed and initTracer() called, every query (Model.find(), findOne(), updateOne(), ...), aggregation (Model.aggregate()), and document.save() call is automatically wrapped in a db-type span, timed with the actual round trip, and its call site captured for the 📍 file:line shown in the terminal reporter.

Scope decision: exec/save chokepoints

This plugin patches Query.prototype.exec, Aggregate.prototype.exec, and Model.prototype.save — not every individual model-level helper. Model statics like Model.find() build a Query and return it as a thenable that calls exec() internally, so patching exec captures both await Model.find() and await Model.find().exec() identically, with the full round trip including query construction. save lives on Model, not Document, so that's what's patched for doc.save() calls.

Known limitation (v1): change streams, cursors (.cursor() / for await iteration without exec), and raw mongoose.connection.db driver calls bypass these chokepoints and are not instrumented.

Security

Only the operation and collection name are captured (e.g. mongoose.find(User)) — never query filters, update payloads, or document contents.

Manual usage

import { mongoosePlugin } from "@trace-dev/plugin-mongoose";
import { registerPlugin } from "@trace-dev/core";

registerPlugin(mongoosePlugin);

Normally unnecessary — @trace-dev/core's auto-detection handles this for you.

License

MIT