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

generic-repository

v1.5.11

Published

Generic repository pattern implementation for node.js. Currently supports mongo and in-memory(testing) databases.

Downloads

15

Readme

generic-repository

Build Status

Generic repository pattern implementation for node.js. Currently supports mongo and in-memory(testing) databases.

Why would i use this?

You want to separate your business logic from your datalayer easily, with a typed promise result from your queries

Quickstart

Make connection To your database:

import MongoConnect from '../mongodb_connect';
onReady = new MongoConnect().connect('MY_CONNECTION_STRING');

Just create a new instance of the repository you need, with the appropriate Type passed in like:

db = new MongoDBRepository(SomeObject);

Now you are ready to query!

db.findOne({_id: '12345'}).then(doc: SomeObject => console.log(doc));

But wait.. there's more!

If you are using enviroment variables for your connection string/credentials you don't need to pass it to connect, if you use this variable naming: DB_URI for your connection string DB_USER for your username DB_PASS for your password

Automatically seed your database

In case you have data you always want to have present in your database, you can use the Seed class to check for this data, and insert if needed:

db = new MongoDBRepository<SomeObject>(SomeObject);
seeder = new Seed(db, '_name', locationOfYourSeedFile(s));
seeder.seed();

In this case '_name' is the field that the seeder will use to check if your data already exists

The seeder will look for a SomeObject.seed.js file in the given directory, the structure of this file should look something like this:

export const SomeObject = {
  data: [{
    _id: 'some_id',
    _name: 'a name that is unique'
  },
  {
    _id: 'another_id',
    _name: 'a name that is also unique'
  }]
};
export default SomeObject;