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

@publicissapient/authorizationutil

v1.4.6

Published

Simplistic authorization management - alternative to heavy (though robust) solutions

Downloads

12

Readme

Authorization Util

unit tests

minified

Simplistic authorization management - alternative to heavy (though much more robust) solutions. The core idea is that a user has already been authenticated (like having a JWT, for example), and we now need to effectively manage the authorization for whatever role they may have.

Most simply put, this is intended to allow an initial configuration of mapping authorizations to a set of roles that are available. The functionality is a very small subset of what you may get from something like CASL, but with a miniscul footprint and zero dependencies. If all you need are the very basics, this may suit your needs.

Getting going...

import AuthorizationService from ".";

/**
 * Role definitions somewhere on app initialization
 */
AuthorizationService.defineRole("admin", [
  "can_create_profile",
  "can_edit_profile",
  "can_view_profile",
]);
AuthorizationService.defineRole("employee", [
  "can_edit_profile",
  "can_view_profile",
]);
AuthorizationService.defineRole("customer", ["can_view_profile"]);

/**
 * Example usage:
 *
 * 1. The create button will only render for the admin role
 * 2. The edit button will only render for admin and employee roles
 * 3. The description will display for all three roles
 */
render(
  <>
    {AuthorizationService.userCan(currentRole, "can_create_profile") && (
      <Button>Create Profile</Button>
    )}

    {AuthorizationService.userCan(currentRole, "can_edit_profile") && (
      <Button>Edit Profile</Button>
    )}

    {AuthorizationService.userCan(currentRole, "can_view_profile") && (
      <p>A profile description...</p>
    )}
  </>
);

Test

npm run test

# we also have a ci specific test command that outputs coverage
npm run test-ci

Typescript

Typescript was introduced as of v1.2.0.


dennis-nedry-gif-7