Weave Code
Nova Chat Laravel Package
binarcode/nova-chat
Nova Chat adds real-time messaging to Laravel Nova, letting admins and users chat directly inside the dashboard. It provides ready-made chat UI components and backend support for conversations, so you can wire up in-app communication without building it from scratch.
Nova Chat adds a ready-made messaging interface to your Laravel Nova admin panel. It ships with the models, migrations, and Nova components needed to create private conversations between users, so your team can chat in-app without building a custom UI from scratch.
- Drop-in chat UI with a conversation list and message thread
- Eloquent models and migrations for conversations, participants, and messages
- Seamless user integration with your existing auth and user model
- Configurable visibility, authorization, and display options
- Built on Laravel/Nova conventions and easy to extend
Frequently asked questions about Nova Chat
- What is BinarCode Nova Chat used for?
- BinarCode Nova Chat is a Laravel Nova tool that adds real-time internal messaging to the Nova admin panel. It provides Vue chat UI components, models, and Nova resources so operators can create conversations, threads, and direct messages with minimal setup. It is intended for lightweight internal use such as support handoffs, ops coordination, and review notes, not as a general-purpose or customer-facing chat service.
- Does binarcode/nova-chat work with Laravel Nova 4 or Nova 5?
- No, not without a fork. The last release was on 2021-05-13, before Nova 4's Vue 3 rewrite and Nova 5, so Composer constraint resolution against a current Nova install will almost certainly fail. Treat support for Nova 4/5 as a modernization project requiring a Vue 3 component rewrite, tool registration updates, and a Vite asset build, not a simple version bump.
- How do I install binarcode/nova-chat in a Laravel Nova application?
- You need a valid Nova license and a Nova 3.x codebase. Install it with Composer, register the tool in the tools() method of your NovaServiceProvider, then publish and run its migrations and assets as needed. You must also configure a Laravel Echo and Pusher-protocol broadcast stack before real-time messaging works. On Nova 4/5, plan for a fork rather than a direct install.
- What broadcasting setup does Nova Chat require?
- The package assumes Laravel Echo plus a Pusher-protocol broadcast driver, such as Pusher, Ably, or a self-hosted Reverb setup. That adds broadcast infrastructure and persistent message storage as runtime dependencies. Reverb did not exist when the package was released, so using it requires testing and possibly code changes. Confirm which driver the code expects and whether it creates a new vendor relationship.
- Is binarcode/nova-chat still maintained?
- Maintenance risk is high: the repository has roughly 15 stars, zero dependents, and no release since May 2021. There is no active maintainer to triage issues or ship security patches, so any defect becomes your responsibility on day one. The bus factor is one, meaning whoever forks it owns it permanently. Treat the package as a reference implementation rather than a supported dependency.
- Does Nova Chat enforce per-channel authorization or just Nova login?
- This is the key security question to audit before adopting the package. Do not assume that being logged into Nova is sufficient authorization for private conversations; verify whether the tool actually uses Nova gates or policies for channel access. If access is implied only by Nova login, the tool can become a data-leak vector. Add explicit per-channel authorization, rate limiting, and retention rules during any fork.
- Can I use Nova Chat for customer support or multi-tenant messaging?
- It is a poor fit for customer support inboxes, multi-tenant messaging, or anything requiring a public API, mobile client, or message history export. The package is a Nova tool, so its blast radius is the admin UI and its database, not the customer-facing product. It does not provide the tenant boundaries or external interfaces such a feature would need. For those requirements, build a scoped service or use a sanctioned support channel instead.
- What security risks come with using Nova Chat?
- Chat introduces stored user-generated content, so XSS is a risk if messages are rendered without escaping. Private-channel authorization must be explicitly reviewed, and any file or attachment handling needs separate scrutiny. None of these areas will be reviewed upstream because the package is unmaintained. Budget time for authorization review, rate limiting, retention policy, and tests before production use.
- How should I test and prepare Nova Chat for production?
- Test message rendering with malicious payloads to confirm escaping, and verify that unauthorized Nova users cannot read private channels. Cover broadcast connection failures, message persistence, rate limiting, and retention behavior in your test plan. Because there are no upstream fixes, add regression tests around the fork's authorization and attachment handling. Treat production readiness as an owned engineering deliverable, not a package feature.
- What are alternatives to binarcode/nova-chat?
- The strongest alternative is building a scoped equivalent directly on Laravel Reverb and Livewire, which avoids inherited debt; rough estimates put that at 10-15 engineer-days. Forking and modernizing Nova Chat is about 8-12 engineer-days, including Nova 4/5 porting, Reverb migration, authorization review, and tests. Also check whether a sanctioned channel such as Slack or Teams integration already solves the internal coordination need. The package's main value is as a reference implementation, not as a dependency.
Weaver
How can I help you explore Laravel packages today?