Weave Code
Vapor Ui Laravel Package
laravel/vapor-ui
Deprecated: Vapor UI dashboard for Laravel Vapor apps. Adds an in-app interface to browse/search application logs and view failed queue jobs. Replaced largely by Vapor’s own dashboard; no Laravel 11 support.
The Laravel Vapor UI.
Frequently asked questions about Vapor Ui
- Is Laravel Vapor UI still actively maintained or recommended for new Laravel Vapor projects?
- No, this package is officially deprecated and will not support Laravel 11.0 or later. Laravel now recommends using Vapor’s built-in dashboard for log and queue job monitoring, which provides similar functionality with ongoing updates.
- What Laravel versions does Vapor UI support?
- The package only supports Laravel versions below 11.0. If you’re using Laravel 10.x or earlier, you can still install it, but no future updates or Laravel 11 compatibility are planned.
- How do I install Laravel Vapor UI in my existing Vapor project?
- Run `composer require laravel/vapor-ui` in your project directory. The package integrates via Blade views and leverages Vapor’s existing `/logs` and `/jobs` APIs, so no additional backend setup is required beyond ensuring your Vapor app has proper IAM permissions.
- Does Vapor UI work with Vapor 3.x or newer versions?
- No, Vapor UI was primarily tested with Vapor 2.x. Vapor 3.x may introduce breaking changes to the underlying APIs it relies on, so compatibility is not guaranteed. Check the package’s GitHub issues for any reported conflicts.
- Can I use Vapor UI alongside third-party monitoring tools like Datadog or Sentry?
- Yes, but it’s redundant since Vapor’s native dashboard now covers similar functionality. Third-party tools may offer more advanced features, so evaluate whether Vapor UI’s simplicity justifies the integration effort, especially given its deprecated status.
- Will Vapor UI add significant AWS costs to my Lambda deployment?
- The package itself doesn’t introduce major costs, but frequent log searches or high traffic to the UI could increase Lambda invocations or CloudFront requests. Since it’s a frontend layer, costs depend on how often the dashboard is accessed in production.
- How do I migrate from Vapor UI to Vapor’s native dashboard?
- Replace the `vapor-ui` routes in your Laravel app with redirects to Vapor’s dashboard (e.g., `/vapor/logs`). Test thoroughly in a staging environment to ensure no functionality gaps, especially for advanced log filtering or queue job inspection features.
- Are there any security risks using Vapor UI in production?
- Since the package is deprecated and no longer maintained, it may lack updates for CVEs in dependencies like Blade or the AWS SDK. Ensure your Vapor app’s IAM roles are strictly scoped to minimize exposure, and consider migrating to Vapor’s dashboard for security patches.
- Does Vapor UI support advanced log filtering or custom queries?
- The package provides basic log browsing and search functionality, but it lacks the advanced filtering or custom queries available in Vapor’s native dashboard or third-party tools. If you need granular log analysis, Vapor’s dashboard or dedicated monitoring tools may be better options.
- What should I do if I encounter compatibility issues with Laravel 10.x or Vapor 2.x?
- Check the package’s GitHub issues for reported bugs or workarounds. Since maintenance is nonexistent, you may need to fork the repository or manually patch conflicts. Document your changes and plan to migrate to Vapor’s dashboard as soon as possible, especially after upgrading to Laravel 11.
Weaver
How can I help you explore Laravel packages today?