Weave Code
Filament Oops Laravel Package
saasykit/filament-oops
Filament Oops adds simple error tracking to your Filament admin panel. It captures exceptions from your Laravel app and lets you browse, search, and inspect error details, stack traces, and context so you can debug issues without leaving Filament. Designed for quick setup and a clean, native Filamen...
Never accidentally edit your Filament production panel again! Filament Oops displays a clear 'Production' warning, helping you avoid updating your production Filament panel by mistake.
Frequently asked questions about Filament Oops
- What is saasykit/filament-oops used for?
- Filament Oops is a Laravel package for Filament admin panels. It displays a clear Production warning to help prevent accidental edits to a production Filament panel, and the package blurb also describes in-panel error tracking for browsing exceptions, stack traces, and context. Confirm the exact feature set in your installed version before relying on it.
- How do I install Filament Oops in a Laravel app?
- Install it with Composer using composer require saasykit/filament-oops, then register the plugin in your Filament panel provider as described in the package docs. Because it is a Filament plugin, you need a Filament-based admin panel; it is not a standalone Laravel debugging tool. Check the README for any publish or migration steps.
- Does Filament Oops support Filament v5?
- Release 2.1.0 is noted as adding Filament v5.0 support, so that is the clearest compatibility signal available. The release note does not state whether Filament v4 support was retained or dropped, so check composer.json constraints before upgrading. If you run Filament v4, test dependency resolution in a branch first.
- Will Filament Oops work with Laravel 10, 11, or 12?
- The provided context does not list Laravel framework constraints. Because it is a Filament plugin, its Laravel support will usually track the Filament major you use, but you should verify the composer.json requirements for laravel/framework and PHP. Do not assume Laravel version support from the Filament v5 note alone.
- Is Filament Oops safe to install in production?
- Its stated purpose includes showing a Production warning to reduce accidental edits, so the warning itself is intended for production panels. However, if you enable error tracking, review what exception context is stored and who can access it in Filament. Treat production installation as a configuration and access-control decision, not just a Composer install.
- Can I customize the production warning message in Filament Oops?
- The provided overview does not document configuration options for the warning text or styling. Check whether the package publishes config or views, and review the README for panel registration options. If no config is published, assume the warning is fixed until you confirm otherwise.
- Does Filament Oops replace Sentry, Telescope, or Laravel's exception handler?
- The blurb describes capturing exceptions and browsing them inside Filament, which is useful for quick in-panel debugging. It does not claim to replace full application monitoring, alerting, or Laravel Telescope, and no such comparison is provided. Use it as a convenience layer and keep your existing monitoring for production incident response.
- How do I configure error tracking and search in Filament Oops?
- The available context says you can browse, search, and inspect error details, stack traces, and context from Filament, but it does not list config keys or setup commands. Look for published config, migrations, and panel plugin registration in the README. If the docs are thin, inspect the package source for the actual configuration surface before adopting it.
- Is saasykit/filament-oops actively maintained?
- The only evidence provided is release 2.1.0 with Filament v5.0 support, which suggests the package is being updated for current Filament. It does not establish a long-term support window, maintainer team size, or security policy. For a production dependency, check the repository activity, issue tracker, and release history directly.
- When should I avoid using Filament Oops?
- Avoid it if your admin surface is not built with Filament, because a Filament plugin cannot be partially adopted into a Blade or Livewire admin without adopting Filament first. Also avoid it if you need a guaranteed support contract or a CI-verified compatibility matrix that the available release note does not provide. For critical production debugging, pair it with a dedicated monitoring service.
Weaver
How can I help you explore Laravel packages today?