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

@inlayphp/permission-manager-vue

v0.3.11

Published

Vue role and permission management screens for Inlay panels.

Readme

Inlay Permission Manager for Vue

npm License

Vue role and permission management screens for Inlay panels

@inlayphp/permission-manager-vue renders the Inertia pages published by inlayphp/permission-manager. It is the Vue counterpart of @inlayphp/permission-manager-react and answers the same page names with the same props, so a panel can switch renderers without the PHP plugin changing.

Optional package boundary

This renderer is not part of the lean inlayphp/inlay frontend installation. Add it only when both conditions are true:

  1. the Laravel application installed and registered inlayphp/permission-manager;
  2. the target Inlay panel uses Vue.

Installing the npm package does not install the PHP plugin, create Spatie tables, register routes, or grant access. Authorization always remains on the Laravel side — these pages render what the server already decided the visitor may see.

Install

pnpm add \
  @inlayphp/permission-manager-vue \
  @inlayphp/forms-vue \
  @inlayphp/tables-vue \
  @inertiajs/vue3 vue

The standalone PHP plugin must also be installed and registered. It depends on inlayphp/authorization-spatie, which needs its Spatie migrations and user model integration configured.

Pages

Register these against the page names the plugin publishes:

| Component | Page | | --- | --- | | RoleIndexPage | inlay-permission-manager/roles/index | | RoleFormPage | inlay-permission-manager/roles/form | | PermissionIndexPage | inlay-permission-manager/permissions/index | | PermissionFormPage | inlay-permission-manager/permissions/form | | UserAccessFormPage | inlay-permission-manager/users/access | | AccessAuditPage | inlay-permission-manager/audit |

import {
  AccessAuditPage,
  PermissionFormPage,
  PermissionIndexPage,
  RoleFormPage,
  RoleIndexPage,
  UserAccessFormPage,
} from '@inlayphp/permission-manager-vue'

PageShell, Surface, Flash, PrimaryLink, BackLink, and PermissionMatrix are exported as well, for an application that wants to compose its own screens from the same parts rather than mount the pages as published.

Styling

The pages read the --inlay-* custom properties the surrounding panel declares and name their elements with the shared data-slot vocabulary, so a stylesheet written against the React pages selects the same elements here. The permission matrix's controls come from @inlayphp/ui, which is where the shared control class lives so the two renderers cannot drift apart.