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

@yikesable/rbac

v0.1.0

Published

Vanilla role-base access control library

Downloads

4

Readme

@yikesable/rbac

Vanilla role-base access control library

npm version npm downloads neostandard javascript style Module type: ESM Types in JS Follow @voxpelli@mastodon.social

Usage

import { addRolePermission } from '@yikesable/rbac';

const { hasPermission } =
  addRolePermission('admin:foo', '*')
    .addRolePermission('editor:bar', 'wow')
    .done();

if (hasPermission('admin', 'foo', 'create') === true) {
  // "create" operation allowed for "foo" for role "admin"
}

API

addRolePermission()

Adds operations that a role is allowed to do on a role.

Each role / context combination can only be set once.

Syntax

addRolePermission('role:context', 'create', 'update', 'delete') => { addRolePermission, done }

Arguments

  • roleWithContextstring – a role / context combination
  • ...operationsstring – the options to be permitted for the combination. If '*' is set then all operations will be permitted.

Returns

An object with these properties:

  • addRolePermission() – chaining that adds operations for another role / context combination
  • done() – completes the creation chain and returns an object with a hasPermission() property

hasPermission()

Syntax

hasPermission('role', 'context', 'operation') => boolean

Arguments

  • rolestring[] | string – the role to check permission for. If an array is given then as long as one of the roles has permission true will be returned
  • contextstring – the context to check permission for, eg blogpost
  • operationstring | '*' – the operation that should be permitted by the role in the context – eg. create, update, update-own or similar

Returns

A boolean that indicates whether the role has permission or not.

Types

import type { PermissionCrudOperation } from '@yikesable/rbac';

declare module '@yikesable/rbac' {
  interface PermissionRoleList {
    admin: true;
    editor: true;
  }

  interface PermissionContextOperations {
    foo: PermissionCrudOperation; // 'create' | 'read' | 'update' | 'delete'
    bar: 'wow' | 'yay';
  }
}
  • PermissionRoleList – extendable interface where keys represent role names and should be string, value can be whatever but true is recommended
  • PermissionContextOperations – extendable interface where represent context names and should be string, value represents possible operations for that context and should be a union of string values

role and context in addRolePermission() and hasPermission are limited to the values derived from above interfaces and operations gets limited to the operations defined in PermissionContextOperations for the context used in those functions.