Filament Developer Login Laravel Package

Getting Started

• Install with Composer:

  composer require outatime-io/filament-login-shortcut
  

• v1.0.2 requires Filament 4.7+ or 5.2+. Check your current version before updating:

  composer show filament/filament
  

• Register the package’s Filament plugin/service provider in the relevant panel provider, following the package README. Publish any config or views only if the package documents them.
• Clear caches after installation or upgrade:

  php artisan optimize:clear
  php artisan view:clear
  

• First use case: add the login shortcut/callout to a Filament panel login page, typically for local, staging, demo, or internal panels where faster access or login-page guidance is useful. Start by checking the package README, the panel registration snippet, and the rendered /admin/login page.

Implementation Patterns

• Register the shortcut only on panels that need it. If you run multiple Filament panels, enable it per panel rather than globally.
• Treat the shortcut as a UI/auth convenience, not a replacement for Filament authentication or authorization. Keep normal login policies, rate limiting, and access controls intact.
• Gate the feature by environment or configuration where appropriate:

  // Example intent: only expose shortcut UI where it is safe.
  if (app()->environment(['local', 'staging'])) {
      // register package plugin/configuration
  }
  

• When upgrading Filament, update the package in the same Composer operation so constraints resolve together:

  composer update filament/filament outatime-io/filament-login-shortcut
  

• Add a lightweight feature test or smoke check for the login page so custom login views, panel themes, and Filament upgrades do not silently break the shortcut:

  $this->get('/admin/login')->assertOk();
  

• If the package exposes config, keep environment-specific values in .env rather than editing vendor files. Use Filament render hooks or custom login views only when the package does not provide a supported extension point.

Gotchas and Tips

• v1.0.2 is a compatibility fix, not a feature release. Its main impact is the raised Filament minimum: installs on older Filament releases are now rejected during composer update.
• If you are pinned to Filament older than 4.7/5.2, do not force v1.0.2 with constraint overrides or --ignore-platform-reqs. Stay on v1.0.1 or upgrade Filament first.
• The render error Unable to locate a class or view for component [filament::callout] means the installed Filament version does not provide the filament::callout Blade component. The correct fix is upgrading Filament to a supported version, not overriding the package constraint.
• After upgrading, run php artisan view:clear and php artisan optimize:clear. Stale compiled views can make it look like the shortcut or callout is missing.
• If the shortcut does not appear, check panel registration first, then custom login page overrides, published views, and panel theme customizations that may bypass the package’s render location.
• Use the package primarily in non-production or tightly gated panels. Avoid exposing shortcut UI in public production login pages unless you have explicitly reviewed the security implications.