- How do I install naoray/nova-json in a Laravel Nova application?
- Install it with composer require naoray/nova-json. Laravel package auto-discovery handles the service provider wiring, so you typically just add the field to a Nova resource. The basic integration does not require publishing config files. Smoke-test an existing resource after installation.
- Does naoray/nova-json support Laravel 12, Nova 5, and PHP 8.4?
- Version 4.1.0 is described as a compatibility release that adds Laravel 12, Nova 5, and PHP 8.4 support without stated breaking changes. Check composer.json to confirm the exact version constraints and minimum PHP floor. Nova 5 is a commercial upgrade, so the package release removes a dependency blocker but does not itself authorize the platform move.
- Can naoray/nova-json edit deeply nested JSON or only flat key-value data?
- The package is positioned as a structured interface for JSON columns, but the overview emphasizes spreading a JSON column across multiple fields rather than arbitrary deep tree editing. Confirm whether your nested structure is supported by testing the field on a representative document. For deeply nested or schema-driven data, verify per-key validation behavior before committing.
- How does validation work for JSON fields in naoray/nova-json?
- The package can complement Nova validation, but validation behavior should be confirmed rather than assumed. The key questions are whether Nova rules apply per field and how malformed or schema-drifted JSON is handled on render. Test create, update, and detail views with invalid payloads in staging. Do not rely on the UI alone to enforce data integrity.
- Is naoray/nova-json safe for untrusted or malformed JSON in production?
- JSON columns are untyped, so malformed or schema-drifted documents can throw during render. Treat any raw echo of stored values as an XSS risk and confirm that content is escaped on index and detail views. The package lives inside the Nova request/render lifecycle and adds no storage or external services. Validate and sanitize JSON at the application boundary before exposing it in Nova.
- How do I upgrade naoray/nova-json from v4.0.0 to v4.1.0?
- Bump the Composer constraint and run composer update naoray/nova-json. The v4.1.0 release is described as additive compatibility, so it should be a drop-in for teams already on v4.0.0. Smoke-test an existing Nova resource and check the field registration. Expect under a day including verification.
- Does naoray/nova-json support mixed Laravel and Nova versions during a rollout?
- That depends on whether v4.1.0 widened the Composer constraints or performed a hard bump. A widened OR-set can let the same app version run across a mixed fleet; a hard bump would strand anyone mid-upgrade. Inspect composer.json before a fleet rollout. If you operate multiple Nova apps at different versions, constraint flexibility matters more than the feature set.
- Is naoray/nova-json actively maintained, and what is the bus factor?
- The assessment describes effectively one primary maintainer plus a first-time contributor on the v4.1.0 release. Low velocity is acceptable for a small field package, but abandonment risk is real and there is no visible fallback fork strategy. Longevity is tied to Nova's closed-source field API as well as Laravel's release cadence. Identify an internal owner if upstream goes quiet.
- What are alternatives to naoray/nova-json for editing JSON in Laravel Nova?
- Nova includes built-in text and code fields that can display raw JSON, but they do not provide structured per-key editing. naoray/nova-json complements those fields by spreading a JSON column across multiple editable fields. Evaluate whether you need structured editing and validation versus a simple code editor. Any alternative must also track Nova's commercial field API.
- How should I test naoray/nova-json before deploying to production?
- Create a staging branch on Laravel 12 and PHP 8.4 with Nova upgraded, then add nova-json v4.1.0 and verify field registration. Regression-test the full field lifecycle: index display, detail render, create, update, and validation. Run PHP 8.4 with deprecation reporting enabled because older releases may emit notices even if they still function. Confirm escaping of stored JSON on index and detail views.