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-permission

v1.0.1

Published

Add permission functionnality to a mongoose schema

Downloads

8

Readme

mongoose-permission

NPM version Dependency Status Dependency Status

This is a mongoose plugin to add permissions to a model :

  • A model can have multiple permissions at once
  • "Master" permissions can be defined by having children permissions
  • If a children permission is revoked then master will be revoked too.
  • Granting a master permission also grant all children

It may not be the best logic, but it suited to my personnal needs. It gives the possibility to easely grant or revoke permissions to an user and handle automatically master permissions. This way I can avoid the fact that an user doesn't have all permissions needed to make a task.

Installation

npm install --save mongoose-permission

Usage

'use strict';

var UserSchema = new require('mongoose').Schema({
  name: String,
  password: String
});

//Permission tree initialization
UserSchema.plugin(require('mongoose-permission'), {
    'administrate': ['create', 'read', 'update', 'delete'],
    'manage articles': ['publish', 'write'],
    'write': ['read'],
    'read': ['']
});

var User = mongoose.model('User', UserSchema);

var chris= new User({name: 'chris pi' ... });

chris.grant('administrate'); //Pass any number of permissions separated by ',' : chris.grant('read','write',...)

console.log(chris.can('administrate')); // true
console.log(chris.can('read')); // true
console.log(chris.can('write')); // false
console.log(chris.can('create')); // true

chris.revoke('administrate');

console.log(chris.can('administrate')); // false
console.log(chris.can('read')); // true
console.log(chris.can('write')); // false
console.log(chris.can('create')); // true

...

chris.grant('administrate','write');
console.log(chris.can('administrate')); // true
console.log(chris.can('read')); // true
console.log(chris.can('write')); // true
console.log(chris.can('create')); // true

...

//Revoking children if needed
chris.revoke('administrate', true);
console.log(chris.can('administrate')); // false
console.log(chris.can('read')); // false
console.log(chris.can('write')); // false => write need read, but lost by revoking children
console.log(chris.can('create')); // false

This plugin adds a permissions String array to a schema, containing all permissions granted, plus a bunch of methods :

  • Granting : grant(permission1[, permission2[, permission3 ...]])
  • Revoking : revoke(permission, revokeChildren)
  • Chicking: can(permission)
  • Getting possibilities : getAvailablePermissions()

It it required that you pass in permissions to the plugin. This way you cannot grant a user to generated permissions, I may add a possibility to do this later, but my main goal by doing it this way is to have to think to all possibility and not to deviate and invent new ones every now and then...

You can use this in a middleware function to check if an user can perform or access a specific page or functionnality.