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

mongodb-mql-engines

v0.0.4

Published

Exposes, on demand, engines used by the MongoDB IntelliJ Plugin for index suggestions.

Readme

mongodb-mql-engines

Exposes, on demand, engines used by the MongoDB IntelliJ Plugin for index suggestions.

Example Usage:

const mql = require('mongodb-mql-engines');

const sampleDocuments = [ { a: 1, b: 2 }, { a: 5, b: true } ]

const ns = mql.analyzeNamespace({ database: "mydb", collection: "mycoll" }, sampleDocuments)
const query = mql.parseQuery({ a: 1, b: 2 }, ns)
const index = await mql.suggestIndex([ query ])

console.log(index);

Expected output:

{ index: { a: 1, b: 1 }, coveredQueries: [ { a: 1, b: 2 } ] }

API

analyzeNamespace(namespace: { database: String, collection: String }, sampleDocuments?: Array): Namespace

Creates a new namespace reference with the data distribution calculated from the sample documents. If no sample documents are provided, it won't use this information for suggesting indexes or running any other engine.

The more documents are provided as a sample, the better the index suggestion will be.

mql.parseQuery(query: Json, namespace: Namespace): Query

Parses a JSON query, defined as plain JSON or relaxed EJSON and attaches it to the provided namespace.

mql.suggestIndex(queries: Array): SuggestedIndex

Analyses all the provided queries and returns the best index to cover all of them. In case only a single query is analysed, provide an array with that single query.