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

mongoose-user-resolver-plugin

v0.1.1

Published

Automatically resolves the owning user of every model.

Downloads

3

Readme

Mongoose-User-Resolver-Plugin

Automatically resolves the owning user of every model.

Installation

npm install mongoose-user-resolver-plugin

Usage

The plugin is configured by using the plugin function like any other mongoose plugin.

Assume you have a model project with a name and a owning user:

var ProjectSchema = mongoose.Schema({
    name: {
        type: String,
        required: true
    },
    user: {
        type: mongoose.Schema.ObjectId,
        ref: 'user',
        required: true
    }
});

The resolver-plugin would then be configured like this:

ProjectSchema.plugin(require('mongoose-user-resolver-plugin'), {path: 'user', stop: true});

The stop attribute indicates that the provided id is the userId, so that the plugin would not try to retrieve the referenced model as it is unnecessary here.

Calling getUserId on a project instance would then resolve to the path user. The clue is that this does also work on instances that reference this project, for example:

Assume we have another model file:

var FileSchema = mongoose.Schema({
    basename: {
        required: true,
        type: String
    },
    project: {
        required: true,
        type: mongoose.Schema.ObjectId,
        ref: 'project'
    }
});
FileSchema.plugin(require('mongoose-user-resolver-plugin'), {path: 'project'});

This model references the above project model.

Calling getUserId on a file instance returns the userId that is referenced from the referenced project! With this technique you can easily build authentication and verify-algorithms that are independent from the concrete model.

Code-Quality

Current Jenkins report for this project:

  • BuildStatus
  • Test
  • LastBuild
  • CodeCoverageInJenkins