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

mongo-compare-indexes

v1.1.1

Published

compare indexes in two mongo instances

Readme

mongo-compare-indexes

compare mongo indexes in two instances

Read this in other languages: English | Українська

Use Case

You may need to compare the indexes between different servers/environments (e.g. it can be comparison of the local and dev server, or comparing production environment to staging or uat)

Usage (CLI)

This command requires two URLs provided for target and source mongodb servers to compare their indexes.

It can be done using environment variables TARGET_MONGO_URL and SOURCE_MONGO_URL.

You can define them before executing the command, e.g.

export TARGET_MONGO_URL="mongodb://user:pass@host:port/db_name"
export SOURCE_MONGO_URL="mongodb://localhost/db_name"

and then just run:

npx mongo-compare-indexes run

OR you can define the db URLs inline:

npx mongo-compare-indexes run [options] [source-mongodb-url] [target-mongodb-url]

Example:

npx mongo-compare-indexes run mongodb://localhost:27017/db_name_source mongodb://localhost:27017/db_name_target

Usage (code)

You can also use it within your project using getMissingIndexes method.

Here is an example:

import { getMissingIndexes } from 'mongo-compare-indexes';

async function run () {
  const targetUrl = process.env.TARGET_MONGO_URL; // you can replace it with your own variable
  const sourceUrl = process.env.SOURCE_MONGO_URL; // same here

  console.log("Starting MongoDB index comparison...");
  const missingIndexesResult = await getMissingIndexes(targetUrl, sourceUrl);
  const { missingIndexesSource, missingIndexesTarget } = missingIndexesResult;
  for (const index of missingIndexesSource) {
    console.log(`Missing in source: ${index.collection} - ${index.index_name}`);
  }
  for (const index of missingIndexesTarget) {
    console.log(`Missing in target: ${index.collection} - ${index.index_name}`);
  }
}

run();

Future considerations

  • [ ] Add Unit tests
  • [ ] Add support of --skip-missing-collections option to prevent showing _id indexes for the empty/missing collections
  • [ ] Rewrite with TypeScript