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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@humano/frontend-permissions

v0.2.1

Published

React hooks and small UI helpers for view/action permissions. No data layer included.

Readme

@humano/frontend-permissions

Small, data-agnostic building blocks for view/action permissions in React 18/19:

  • usePermissionCheckerFromFn — memoize (viewId, action) => boolean
  • useViewPermissionscanEditar(), can("custom"), …
  • PermissionGate / useGuardedAction — UI
  • filterMenuByRouteOptions / getFirstAllowedRoute — filter nav trees and pick a default route
  • hasPathAccessInOptions / matchPathToOptions — path matching (pass your router basename explicitly; no default is assumed)

No HTTP client, no auth provider, no hardcoded host or product routes — bring your own.

Install

npm install @humano/frontend-permissions
# or: pnpm add / yarn add

Peer: react ^18 || ^19.

Imports

Recommended root import:

import {
  usePermissionCheckerFromFn,
  useViewPermissions,
  PermissionGate,
  filterMenuByRouteOptions,
} from '@humano/frontend-permissions';

Subpath imports still work:

import { useViewPermissions } from '@humano/frontend-permissions/useViewPermissions';

Menu filtering

  1. Get allowed route keys from your backend (e.g. string list).
  2. Set applicationBasePath to the same value as your React Router basename (or "").
  3. Call filterMenuByRouteOptions(items, allowedPaths, { applicationBasePath, isDevelopment }).

Publish (maintainers)

From a clone of the package:

cd packages/frontend-permissions
npm run build
npm publish --access public
# scope must match your npm organization; see package "name" field

License

MIT – see LICENSE.