Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Filament Local Logins Laravel Package

better-futures-studio/filament-local-logins

A Filament plugin that lets you log in as local users with a single click, making it easy to switch accounts and test different roles during development. Speeds up local workflows, demos, and QA without typing credentials each time.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Developer & QA velocity as a product lever. The package adds one-click local logins ("log in as…") to a Filament panel, so anyone validating a flow can switch roles/personas in seconds instead of hunting passwords or seeding fixture accounts. That shortens the loop between "spec written" and "flow verified," which compounds across every role-gated feature you ship.
  • Scope decisions on multi-role and permission work. When you can impersonate an admin, a customer, and a support agent in one click, edge-case coverage of role/permission matrices becomes cheap. This directly informs how far you can push role complexity (tiers, org scoping, delegated admin) without ballooning QA cost.
  • Demo and stakeholder-review readiness. For sales demos, design reviews, and investor/exec walkthroughs, being able to jump into a seeded persona on a staging-like environment removes the "can you log in as…" dead air. Worth considering as a standing capability for any demo environment you maintain.
  • Build vs. buy/borrow. The underlying capability is small enough to hand-roll, but it is also not differentiated work. Treat this as a commodity dev-tooling dependency: adopt it, pin it, gate it to non-production, and spend engineering attention on product surface instead.
  • Upgrade-risk budget for Filament major versions. The 1.5.1 release explicitly maintains native styling across Filament 3–5 and, notably, no longer requires consumers to compile the package's Tailwind classes. That means one less asset-pipeline chore and one less "our admin UI broke when we bumped Filament" incident — a real, if modest, reduction in the cost of staying current on your admin framework.

When to Consider This Package

Consider adoption when:

  • Your admin/internal surface is a Filament panel and your team or QA routinely needs to view the app as different users.
  • You run local or ephemeral preview environments and want persona switching without seed-password management.
  • You have (or expect) multiple roles or tenant scopes, making manual re-login friction a recurring tax.
  • You want this without touching your front-end build — the 1.5.1 fix specifically targets consumers who don't compile package Tailwind, so it fits teams that treat vendor assets as opaque.
  • You are on, or plan to move to, Filament 3, 4, or 5 and want the tool to survive that upgrade rather than becoming a migration chore.

Look elsewhere or skip when:

  • The app is not Filament-based, or your admin surface is bespoke.
  • You cannot guarantee environment gating — this class of tool must be hard-disabled in production; if your config/deploy story can't enforce that, don't ship it.
  • Your need is actually audited impersonation for support staff in production. That's a security-sensitive, logged, permissioned feature and should be built in-house with an audit trail, not satisfied by a local-dev convenience package.
  • You already have a stable fixture/seed + password strategy and persona switching isn't a measured bottleneck. Adopt on demonstrated friction, not by default.

How to Pitch It (Stakeholders)

For executives (one line): A small, free dev-tooling dependency that lets our team test and demo the product as any user in one click — faster QA and smoother demos, zero customer-facing surface, disabled outside local environments.

For engineering: A Filament plugin adding local-login buttons to admin panels, version 1.5.1. This release is a patch, non-breaking: it fixes button layout on Filament 5 without requiring us to compile the package's Tailwind classes, adds regression coverage for that build-independent layout, and preserves native Filament styling across 3–5. Practical read: near-zero integration cost, no asset-pipeline changes, and it stays compatible as we move Filament majors. Recommendation: adopt as a dev-only dependency, pin the version, and enforce environment gating in config so it can never be reachable in production. Revisit only if we later need audited production impersonation — that's a separate, in-house build.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
hsluv/hsluv
seampact/codegen
seampact/hooks
seampact/ir
mehedimi/laravel-amp-mail
happones/laravel-vue-i18n-generator
jwerd/inertia-table
siberfx/flysystem-wasabi
hollyit/token-replace
ippanelcom/laravel-sdk
adachsoft/changelog-linter
adachsoft/collection
payerurl/telegrambot-crypto-payment-instant-payout
dskripchenko/laravel-hybrid-search
riorizkyrainey/lara-ced
mehedimi/static-vel
zharp/zharp
nonsapiens/bigquery-model-sync
lgu-bayambang-ict-office/lgu-laravel-development-standards
andydefer/laravel-support