Weave Code
Nova Echo Laravel Package
coreproc/nova-echo
coreproc/nova-echo integrates Laravel Echo with Laravel Nova, enabling real-time broadcasting and live updates for Nova resources, dashboards, and custom tools. It helps admin panels listen for broadcast events and refresh without polling, making interfaces more responsive.
Adds a configured Laravel Echo to your Laravel Nova app
Frequently asked questions about Nova Echo
- What does coreproc/nova-echo do for Laravel Nova?
- It is a thin integration layer that connects your Nova admin panel to Laravel Echo so the Vue SPA can subscribe to broadcast channels and react to events. Instead of polling, Nova resources and dashboards can refresh when models are created, updated, or deleted. It adds no new backend service, table, or queue topology of its own.
- How do I install coreproc/nova-echo?
- Install it with Composer using composer require coreproc/nova-echo, then publish its configuration file. You apply the package's trait or field to the Nova resources you want to make live, and make sure the underlying models broadcast events implementing ShouldBroadcast with a broadcastOn method pointing at the configured channel. Verify how the package injects its JavaScript into your Nova version before rolling it out.
- Which Laravel Nova versions are supported?
- The last release was in March 2023, which predates Nova 5, so treat Nova 5 support as unverified until you test it. Nova's SPA internals change between minor versions, so confirm compatibility for your exact Nova major before adopting. If you are on Nova 4, the odds of a working drop-in are considerably better than on Nova 5.
- Does it work with Pusher, Ably, and Laravel Reverb?
- Yes, it works with any broadcaster your Laravel Echo setup supports, including Pusher, Ably, and self-hosted Laravel Reverb. The package is a presentation-layer adapter, so broadcaster choice is yours and is configured in Echo and your broadcasting config rather than in the package. Managed services are metered and cost money, while Reverb requires you to run websocket infrastructure yourself.
- How does channel authorization work with Nova's authentication guard?
- Private and presence channels must be authorized against Nova's guard, so your broadcast authorization callbacks need to resolve the Nova user correctly rather than assuming the default web guard. If channels are not scoped by tenant or role, any authenticated admin can subscribe to data they should not see. Review your channel definitions carefully because this is a real horizontal data exposure risk in a privileged admin panel.
- Will live updates respect Nova's filters, sorting, and pagination?
- Not reliably for inserts. Nova's index is paginated, filtered, and sorted on the server, so the browser cannot know whether a newly created record matches the active filter set or belongs on another page. Updates and deletes on visible rows generally behave correctly, while inserts are best treated as approximate or appended optimistically.
- Could live updates overwrite unsaved changes in a Nova form?
- Yes, that is a genuine risk if you enable live updates on detail or edit views. An incoming broadcast event can patch the record state while a user is editing, replacing unsaved input and causing data loss. Add a suppression rule while a form is dirty, or show a record changed, reload prompt instead of patching silently.
- Do I need a queue worker to use this package?
- You need a queue worker if your broadcast events are queued, which is the recommended configuration in Laravel. The package itself adds no queue topology, but the events it listens for still have to be broadcast by your application. Without a running worker, queued events simply will not fire and the panel will appear not to update.
- Is coreproc/nova-echo actively maintained and safe for production?
- Adoption is thin, with roughly 19 stars, and the repository source is unresolved in the package metadata, which is a blocker for something installed into a privileged admin panel until provenance is verified. Because Nova is commercial and closed source, breakage from a Nova upgrade will likely be silent: panels just stop updating rather than throwing errors. Plan for a fork or in-house patch if upstream goes dormant.
- How does it compare with writing my own Echo integration in a Nova tool?
- A custom Nova tool or asset bundle gives you full control of the JavaScript build, which matters because injecting Echo into Nova's compiled SPA is where most drop-in claims fail. This package saves you that initial scaffolding if it works with your Nova version, but you still own the build when Nova upgrades. Teams already broadcasting model changes for other consumers get the most value; Nova-only teams should weigh the recurring broadcaster cost.
Weaver
How can I help you explore Laravel packages today?