- What is marshmallow/live-update and what does it do?
- marshmallow/live-update is a Laravel Nova extension that lets you edit Nova resource records directly from the resource index page instead of opening each record's detail view. The package description is 'Edit your Nova resources from the index page,' and the technical assessment describes it as a thin Nova package with a service provider and bundled Vue/JS assets that override Nova's index row rendering. The concrete feature evaluated here is inline editing inside Nova's closed-source frontend, not a general Laravel websocket or real-time toolkit. Treat the broader 'live-updating data' blurb as positioning, and evaluate the index-edit workflow itself.
- How do I install marshmallow/live-update in a Laravel Nova app?
- Installation follows the normal Laravel package path: require marshmallow/live-update with Composer, then register its service provider if your Laravel version does not auto-discover it. The assessment notes the package is small, with a service provider and bundled Vue/JS assets, but the provided README excerpt does not include exact commands or asset-publishing steps. You must already have a valid Nova license and a working Nova installation. Check the repository README for any publish or build step before installing in staging.
- Which Laravel and Nova versions does marshmallow/live-update support?
- The provided context does not state supported Laravel or Nova versions, so do not infer them from the marketing description. Read composer.json for version constraints and check whether the package targets Nova 4, Nova 5, or both. The assessment warns that Nova 4 to 5 introduced frontend changes and that a package this small almost certainly targets one major. Pin the exact package version and your Nova major in composer.json before testing.
- Does it respect Nova policies and field-level authorization when editing inline?
- This is the highest-risk question and must be answered by reading the package source, not by assumption. Inline editing creates write paths from a screen that Nova historically treated as read-only, so every update should go through Nova resource policies, field authorizedToUpdate checks, and validation rules. If the package posts raw attributes directly to the model, you have a privilege-escalation surface that code review can easily miss. Test with restricted users and field-level authorization rules in staging before any production use.
- Which Nova field types can I edit from the index page with this package?
- The provided materials do not list supported field types. Expect basic scalar fields such as text, number, and select to be the likely target, while relationships, file uploads, and computed fields are the usual gaps in index-editing implementations. Verify each field type you rely on in a staging Nova instance, including validation and empty-state behavior. If your resources depend on relationship or file fields, plan for a fallback to the standard detail-view edit form.
- Is marshmallow/live-update production-ready?
- The assessment rates technical risk as high: the package has 3 stars, 0 dependents, a single-org maintainer, and no issue history to mine. There is no evidence of production usage, so you would effectively be the first integration test. Abandonment is described as the base case rather than the tail case. Adopt it only with pinned versions, staging coverage, and a budget to reimplement the feature in-house after a Nova upgrade.
- Will it work with Filament, Livewire, Inertia, or a non-Nova Laravel admin panel?
- No. marshmallow/live-update is built specifically against Laravel Nova's closed-source frontend contract, so its conceptual model does not transfer to Filament, Livewire, Inertia, or API-first admin panels. The assessment explicitly says it is not a fit for those stacks. If you are not already standardized on Laravel plus Nova, evaluate native Filament inline-editable columns or a custom Livewire table instead.
- How should I handle Nova upgrades if I depend on this package?
- Pin both the exact package version and the Nova major version in composer.json, then run the package against a staging Nova instance before any Nova upgrade. Add the Nova version bump to your release checklist as a hard gate, because the package's compatibility window is defined by Nova's release schedule, not by this maintainer. The assessment notes no known commitment from the author to track Nova releases. Treat any Nova major upgrade as a potential breakage until proven otherwise.
- Does inline editing trigger model events, validation, and audit trails like the normal Nova update flow?
- That is not stated in the provided context and should be verified in source and tests. The standard Nova update flow is expected to emit model events, apply validation rules, and preserve audit trails, but a small index-editing package may bypass parts of that flow or post raw attributes. Check observers, policies, validation, and any audit-log package behavior with a staging record before trusting it for data stewardship. If auditability is a compliance requirement, require proof rather than assuming parity.
- What are the alternatives to marshmallow/live-update for inline editing in Laravel?
- For Nova users, the alternatives are a custom Nova field or action, or using this package as a reference implementation and building the index-edit surface in-house so you control authorization and Nova upgrades. Nova has no first-party inline index editing according to the assessment, which is why the UX gap is real. Outside Nova, Filament offers inline-editable table columns, and Livewire or Inertia tables can be built to suit your domain. Weigh the low install cost against the higher reversibility cost of teaching operators to depend on an unvalidated index write surface.