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

scope-map

v1.5.0

Published

define a tree of scopes, creating scope strings to provide access without redundancy, and matching agains required scopes

Downloads

3

Readme

scope-map

MIT license minified size 20kb

define trees of scopes, create scope strings to provide access without redundancy, and matching agains required scopes

NPM

usage

creating a scope layout

const scope = require('scope-map');

let layout = scope`
    root {
        scope1
        scope2
    }
`;

creating permissions to target route(s)

let allow_root = layout.allow('root');
let allow_0 = layout.allow('scope1');
let allow_1 = layout.allow('scope1 scope2');
let allow_2 = layout.allow('scope1', 'scope2');
let allow_3 = layout.allow`scope1 scope2`;

/* NOTE:
 * scope map doesnt extrapolate all sub scopes to mean
 * a common parent scope so that parent scopes can later
 * be expanded without giving scopes to unauthorized clients
 */ 
// true
console.log(allow_root != allow_1);

scope modifiers

let allow_read_0 = layout.allow('scope1');
let allow_read_1 = layout.allow('scope1:r');
let allow_write = layout.allow('scope1:w');
let allow_read_write_0 = layout.allow('scope1:rw');
let allow_read_write_1 = layout.allow('scope1:wr');
let allow_exclude = layout.allow('scope1:x');

creating requiremnts

let require_0 = layout.require('scope1');
let require_1 = layout.require('scope1 scope2');
let require_2 = layout.require('scope1', 'scope2');
let require_3 = layout.require`scope1 scope2`;

let require_read_0 = layout.require('scope1');
let require_read_1 = layout.require('scope1:r');
let require_write = layout.require('scope1:w');
let require_read_write_0 = layout.require('scope1:rw');
let require_read_write_1 = layout.require('scope1:wr');

using requiremnts on a scope

// true
console.log(require_0(allow_0));

requirements will remember scopes that are passed to them so that subsequent calls for the same scope run faster

you can also pre prime all requirments so that common scopes run faster. this effects all existing requirments and all future requirements

layout.prime(allow_0);