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 🙏

© 2024 – Pkg Stats / Ryan Hefner

mongo-repo-ts

v1.1.0

Published

Repository Pattern Implementation in TypeScript for MongoDB

Downloads

733

Readme

A Repository Implementation in TypeScript for MongoDB

Installation

npm install mongo-repo-ts --save

Getting Started

Configuration

If you're going to use the built-in sequential IDs, you'll need to create a collection in your MongoDB database called ids.

Defining a Document Type

You can extend the existing RepositoryDocument type, which looks like:

_id: string;
created: string; // ISO date/time

For example, might extend this into a BlogPostDocument like this:

interface BlogPostDocument extends RepositoryDocument {
    title: string;
    body: string;
    author: string;
    comments: Array<BlogPostComment>;
}

Extending the Repository

Next step is to extend the Repository, this is the best way to reuse the repo without having to specify the Collection name and Document Type each time.

class BlogPostRepository extends Repository<BlogPostDocument>
{
    constructor()
    {
        super({
            collectionName: 'blogposts',
            modelRef: 'com.example.blog.post',
            mongoDBConnectionURI: 'mongodb://localhost:27017/my_db',
            mongoDBDatabase: 'my_db',
            increments: true,
        });
    }
}

Note the parameters passed in the options to the parent constructor are:

  • Collection Name - the name of the MongoDB collection where your documents are stored
  • Model Reference - a unique namespace for this type of document
  • Mongo DB connection string
  • Mongo DB database name
  • Whether or not to use sequential model IDs instead of Mongo's built-in ObjectID

I highly recommend you set your connection URI using environment variables to ensure your password is not stored in code.

The repository will automatically generate sequential IDs for you when you create documents without an ID. If you'd rather use MongoDB's built-in ObjectIDs then set this to false;

Using your Repository

In your code:

const repo = new BlogPostRepository();

List all Documents

repo.getAll().then( items => {
   // Do something with all the items 
}).catch (error => {
    // handle error
});

Get a Document by ID

repo.getByID('123').then( document => {
    // Do something with the document
}).catch(error => {
    // handle error
});

Update a Document

repo.save(document).then( document => {
    // The document that was saved is returned
}).catch( error => {
    // handle error
});

Delete a Document

repo.delete('123').then( result => {
    // Result is true if found & deleted
}).catch( error => {
    // Record was not found
});