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

mongonna

v0.0.3

Published

When You're Gonna use HTTPS for MongoDB

Downloads

4

Readme

Mongonna

Serverless MongoDB. What are you ... mongonna do about it?

naming things is hard

Why

Atlas App Service leaves a lot to be desired. If you're using Mongo, you just kind of wanted to use Mongo the way it was intended!

How

ES6 Proxies. And some TypeScript magic. Chain it all together, tell Mongonna about your Mongo Client, because it's a peer dependency and its your types. We're just the chaining and RPC call.

const client = new MongonnaClient<MongoClient>( // <= Tell us your MongoClient typings
  "http://localhost:3000", // <= who should we talk to
  "SUPER_SECRET_SERVER_1" // <= this can be an opaque identifier or real mongo URL
);
await client.db("foo").collection("bar").find({ a: 1 }).toArray();
//           ^         ^                 ^              ^
//            \        |                 |             /
//              \       \                |            /
//                  Every 👏🏻 Call 👏🏻 Is 👏🏻 Typed

Receiving the RPC

It's up to you. You'll get a payload at your url containing

interface MongonnaRequest {
  url: string; // <= self referentia>
  mongoUrl: string; // <= That identifier from above or a full mongo URL
  options: MongonnaClientOptions; // <= The client options object
  chain: MongonnaStack; // <= The chain of calls to execute
}

You can then call applyMongonna wih your client & chain object, and we reflect those calls onto the MongoClient you give us. The resulting object contains the data result from the call, or a serialized error object that can be returned. Send the whole chunk back as JSON!

const { data, error } = await applyMongonna(client, chain);
sendJson(200, { data, error }); // status code 200. The call worked, errors will be rethrown locally