Weave Code
Fluxui Devices Laravel Package
agenticmorf/fluxui-devices
FluxUI + Livewire Volt device and session manager for Laravel, powered by diego-ninja/laravel-devices. View authenticated devices, active sessions, locations, and remotely sign out specific or other devices—Jetstream-inspired UI that drops into the Livewire Starter Kit.
FluxUI Devices adds a polished Flux UI + Livewire (Volt) front-end for device and session management on Laravel, powered by diego-ninja/laravel-devices. It’s designed to drop into the Laravel Livewire Starter Kit, giving users a Jetstream-like experience for viewing trusted devices and active sessions.
Manage authenticated devices, review session details (including location when available), and remotely sign out—without needing Flux Pro for the included device icons.
- Device list with type icons (desktop/tablet/mobile)
- Active session visibility and management
- Remote sign-out per device or “all other devices”
- Location display when session geo data is available
- Flux components + Livewire Volt for a consistent UI
Frequently asked questions about Fluxui Devices
- How do I integrate FluxUI Devices into an existing Laravel Livewire app that isn’t using the Livewire Starter Kit?
- The package is designed to work with Livewire 3/4 and Volt, so you can embed its components anywhere in your app. Just ensure you’ve installed `diego-ninja/laravel-devices` first, added the `HasDevices` trait to your User model, and published the views if you need customization. The components are self-contained and require minimal setup beyond the basic requirements.
- Will FluxUI Devices work with Laravel 10? The docs say 11/12+.
- No, this package explicitly requires Laravel 11 or 12 due to its dependency on Livewire 3/4 and Volt 1.0. If you’re on Laravel 10, you’ll need to upgrade or consider alternatives like `laravel/breeze` or `jetstream` for session management. The package leverages modern Laravel features that aren’t available in older versions.
- Can I customize the device/session tables to add extra columns (e.g., user-specific metadata)?
- Yes, the package is built on `diego-ninja/laravel-devices`, which stores data in a `devices` table. You can extend this table by adding custom columns and updating the `HasDevices` trait or model methods. However, UI customization for these fields will require modifying the published views or creating custom components that override the default ones.
- What happens if I don’t have a Flux UI Pro license? Will the device icons break?
- The package includes fallback Lucide icons for device types (desktop, tablet, mobile) even without Flux Pro. You’ll lose access to Flux UI’s premium icon set, but core functionality—like listing devices, managing sessions, and signing out—remains fully operational. Custom icons can also be manually added by publishing and overriding the views.
- How do I test FluxUI Devices in a CI/CD pipeline? Are there specific edge cases to cover?
- Test the package by simulating multiple devices/sessions using tools like Laravel’s `actingAs()` or browser automation (e.g., Puppeteer). Key edge cases include concurrent sign-outs, location data accuracy (if using geo services), and ensuring the Livewire components update correctly when sessions expire. The package’s unit tests cover basic functionality, but real-world scenarios should be validated in your pipeline.
- Is there a way to disable the auto-registered route and use a custom path instead?
- Yes, the package allows you to customize the route by modifying `config('devices.device_route')` in the published `config/devices.php` file. Simply set your preferred path (e.g., `account/devices`) before registering the route in your `routes/web.php`. This avoids conflicts with existing routes while maintaining the same functionality.
- Can FluxUI Devices replace Jetstream’s session management entirely?
- Yes, if you’re using Jetstream or Breeze and want a Flux UI + Livewire Volt alternative, this package can fully replace their session management features. It provides a modern, reactive UI for devices and sessions while leveraging the same backend logic (`laravel-devices`). However, you’ll need to manually integrate it into your existing auth flows if you’re not using the Livewire Starter Kit.
- Will using Volt (Livewire’s new syntax) impact performance compared to traditional Livewire?
- Volt is designed to be more performant than traditional Blade in Livewire by reducing template parsing overhead. However, the impact on your app depends on the number of devices/sessions being managed. For most use cases, the difference is negligible, but if you’re managing thousands of sessions, test the component’s reactivity under load. Volt’s reactivity model is optimized for real-time updates.
- How do I add FluxUI Devices to a Laravel app that uses Inertia.js instead of Livewire?
- This package is built specifically for Livewire and Volt, so it won’t work directly with Inertia.js. However, you could replicate its backend functionality using `diego-ninja/laravel-devices` and build a custom Inertia-compatible frontend. The UI components are tightly coupled to Livewire, so a full rewrite would be required for Inertia integration.
- Are there any security risks with remote sign-out functionality? For example, could someone brute-force sign out all devices?
- The package inherits security measures from `laravel-devices`, including password confirmation for sensitive actions like bulk sign-outs. However, you should implement additional safeguards in your app, such as rate-limiting the sign-out endpoints or requiring 2FA for bulk actions. Always validate user intent (e.g., via Laravel’s `can()` gates) before allowing critical operations.
Weaver
How can I help you explore Laravel packages today?