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

@knovator/can

v1.2.0

Published

Mostly in Admin Panel there is different roles and according to that each role have different access of routes or functionally. To achieve this we usually write too many condition get it through. In this package include methods like hasAccessOf, hasAccess

Downloads

35

Readme

Can

npm npm npm bundle size

Mostly in Admin Panel there is different roles and according to that each role have different access of routes or functionally.

To achieve this we usually write too many condition get it through.

In this package include methods like hasAccessOf, hasAccessTo, Can which will help you to make you project role based.

For role base structure we use permission object to check if user has acces of it or not. permission object is structured like below,


const permission = {
    [moduleName]: [
        'functionality'
    ]
}

for example,

const permission = {
    user: [
        'list',
        'add',
        'update',
        'delete',
    ],
    design: [
        'list',
        'add',
        'update',
    ],
}

here, above example contains permsions of two modules user and design. we can see that user has add, update, list, delete functionality access and same for design except delete.

hasAccessOf

  • to check access of module.

for example,


const permission = {
   user: [
       'list',
       'add',
       'update',
       'delete',
   ],
   design: [
       'list',
       'add',
       'update',
   ],
}

const userAccess = hasAccessOf(permission, 'user')
//  true

const dahsboardAccess = hasAccessOf(permission, 'dashbaord')
//  false

hasAccessTo

  • to check access of functionality of module.

const permission = {
   user: [
       'list',
       'add',
       'update',
       'delete',
   ],
   design: [
       'list',
       'add',
       'update',
   ],
}

const addUserAccess = hasAccessTo(permission, 'user', 'add')
//  true

const deleteDesignAccess = hasAccessTo(permission, 'design', 'delete')
//  false

Can

  • to conditionally render JSX based on permission. it's same as hasAccessTo but make your code looks better in JSX.

const permission = {
    user: [
        'list',
    ]
}

const addUserAccess = hasAccessTo(permission, 'user', 'add')
//  true

// you can use it in JSX like

...
return (
    <div>
        {addUserAccess && <Button>Add</Button>}
    </div>
)
...

// better way,
...
return (
    <div>
        <Can permissions={permission} module="user" mode="add">
            <Button>Add</Button>
        </Can>
    </div>
)
...

Config

  • you can now define config to disable checking for access

  • just add below code in top level component


import { setConfig } from '@knovator/can';

setConfig({
   turnOff: true
}) // this will not check for access and allow it all.