- What is outatime-io/filament-login-shortcut used for?
- outatime-io/filament-login-shortcut is a small Filament plugin that adds a one-click login shortcut to Filament panel login pages, aimed at local development and admin workflows. It is a presentation-layer convenience, not a core authentication provider. Confirm its exact authentication behavior before relying on it in production.
- How do I install outatime-io/filament-login-shortcut in a Laravel Filament panel?
- Install the package with Composer using outatime-io/filament-login-shortcut, then register the plugin in your Filament panel provider following standard Filament plugin conventions. Confirm your application meets the Filament 4.7+ or 5.2+ requirement before installing v1.0.2. Test the login page render in a non-production environment first.
- Which Filament versions does filament-login-shortcut v1.0.2 require?
- v1.0.2 tightens Composer constraints to Filament 4.7+ on the 4.x line and 5.2+ on the 5.x line. Older Filament versions intentionally fail dependency resolution rather than risking a missing filament::callout component at render time. Always validate the Laravel and PHP constraints in the package composer.json as well.
- Is filament-login-shortcut safe to enable in production?
- The package is described as built for local development with strict non-local safeguards, but any auth-adjacent UI should be reviewed carefully. Confirm whether the shortcut can pre-fill, expose, or bypass credentials before enabling it beyond local environments. Use configuration or a feature flag where available and verify behavior in staging.
- Why does Composer reject Filament 4.6 or older with filament-login-shortcut v1.0.2?
- v1.0.2 requires Filament 4.7+ or 5.2+ so dependency resolution fails earlier instead of hitting a missing filament::callout Blade component when the login page renders. This is the safer trade-off for most teams. Upgrade Filament or remain on v1.0.1 only if you have verified the component exists and accept the runtime risk.
- Does filament-login-shortcut bypass Filament authentication or expose credentials?
- The package is positioned as a login shortcut and presentation-layer convenience, not a core authentication provider, but its exact behavior must be verified. Review whether it pre-fills credentials, exposes demo or test accounts, or changes authentication flow. Do not assume it is production-safe until that review is complete.
- Can I disable the Filament login shortcut outside local development?
- The package claims strict non-local safeguards, and you should also use any available configuration toggle or feature flag for defense in depth. Verify behavior in a production-like staging environment with the same application environment settings. If login-page rendering or access control regresses, remove the plugin or revert the Composer lock.
- Does filament-login-shortcut work with multiple Filament panels?
- It is a Filament plugin registered at the panel level, so you can add it only to the panels where the shortcut is needed. Confirm whether its configuration and safeguards are evaluated per panel and per environment. Review multiple-panel deployments carefully before rolling it out broadly.
- Are there automated tests for the login page and filament::callout component?
- The provided assessment flags test coverage as a key question but does not confirm an automated suite. Check the repository CI for tests that render the Filament login page and exercise the filament::callout dependency. If coverage is missing, add smoke tests for login, logout, and panel access in a non-production environment.
- What are alternatives to filament-login-shortcut for faster Filament local login?
- Alternatives include a custom local-only login route, existing Laravel development login packages, or Filament impersonation tools for admin workflows. Choose based on whether you need a UI convenience or true admin impersonation. Keep any authentication shortcut environment-gated and reviewed before production use.