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

mongoose-base-repo

v1.0.1

Published

Extensible repository interface for MongoDB powered by Mongoose.

Downloads

3

Readme

Mongoose Repository Base

Extensible repository interface for MongoDB powered by Mongoose.

Build Status npm version

Installation

First install Node.js, and MongoDB

$ npm i mongoose-base-repo

or

$ yarn add mongoose-base-repo

Usage

DB Connect

First off we will need to establish a connection with the MongoDB server. Use dbConnect to create that connection.

import { dbConnect } from "mongoose-base-repo";

await dbConnect('mongodb://localhost:27017', 'myDatabaseName');

DbConect can only connect to a single database. If the connection is lost, the base repository will automatically attempt to re-esablish the connection.

See Mongoose for more information on Connection considerations.

Repository Base

Creating a repository is as simple as extending the RepositoryBase<T> class where T is the interface of the app-level model. Here we export an EventRepo as a singleton:

import { RepositoryBase } from "mongoose-base-repo";
import eventRepoConfig from "./config";

// app-level model returned by Get and Save methods
interface IEvent {
  eventId: string;
  eventName: string;
  eventDate: Date;
}

class EventRepo extends RepositoryBase<IEvent> {
  private static exists: boolean = false;
  private static instance: EventRepo;

  constructor() {
    super(eventRepoConfig);
    if (EventRepo.exists) return EventRepo.instance;
    EventRepo.exists = true;
    EventRepo.instance = this;
  }
}

export default new EventRepo();

The RepositoryBase constuctor requires a config object that specifies collection meta data and Schema details.

import { schemaValueTypes as type } from "mongoose-base-repo";

const schemaOptions = {
  eventId: { type: type.String, required: true },
  eventName: { type: type.String, required: true },
  eventDate: { type: type.Date, required: true }
};

// required config object
const config = {
  collectionName: "Events",
  primaryKey: "eventId",
  schemaOptions
};

export default config;

The config defines three fields:

Field | Description --- | --- collectionName | The name of the collection that will live in MongoDB primaryKey | The field that will be set to the auto-generated _id value schemaOptions | A JSON object used to build the schema. Here type is the only necessary value. The primaryKey is expected to be set to required: true