- What is thyyppa/nova-json used for in Laravel Nova?
- It provides a Laravel Nova JSON field for viewing and editing JSON attributes directly in the admin panel. The package spreads a JSON column across multiple fields, which helps manage nested configuration, metadata, and other structured data with formatted output and a smoother editing experience. It is aimed at Nova admin workflows rather than front-end form handling.
- Does thyyppa/nova-json support Laravel 10 and Nova 4?
- Yes, the v4.0.0 release notes state support for Nova 4 and Laravel 10. That makes v4.0.0 the line to evaluate for applications on the current Laravel and Nova stack. Confirm the exact PHP and dependency matrix in the package composer.json and README before upgrading.
- How do I install thyyppa/nova-json with Composer?
- Install it as a Composer dependency using thyyppa/nova-json, then follow the package README for any Nova field registration, configuration, migration, or asset publishing steps. Because v4.0.0 is a major version, check your composer.json constraints and resolve transitive dependency conflicts in a staging branch first. Rerun any package-specific publish or migration commands noted by the maintainer.
- Is thyyppa/nova-json v4.0.0 a breaking change?
- The v4.0.0 release note only says it adds support for Nova 4 and Laravel 10 and does not list breaking changes, dropped versions, or migration steps. A major version should be assumed to include breaking changes or dropped legacy support unless maintainer documentation says otherwise. Review the changelog or upgrade guide and request clarification if none exists.
- Can I use thyyppa/nova-json with Laravel 9 or Nova 3?
- The v4.0.0 release is positioned for Laravel 10 and Nova 4, so it is likely not a drop-in fit for Laravel 9 or Nova 3 applications. Treat those older framework lines as a separate upgrade track and confirm supported constraints before attempting installation. For legacy products, defer unless a parallel Laravel and Nova upgrade is planned.
- How does thyyppa/nova-json spread a JSON column across multiple fields?
- The package is designed to present a JSON column as multiple fields in Laravel Nova so editors can view and edit structured attributes without hand-editing raw JSON. It is intended for nested configuration, metadata, and similar structured data, with formatted output and a smoother editing experience. Test representative JSON payloads in staging to confirm the field mapping matches your schema.
- What PHP version does thyyppa/nova-json v4.0.0 require?
- The provided v4.0.0 release note confirms Nova 4 and Laravel 10 support but does not state a PHP version requirement. Check the package composer.json and README for the exact PHP constraint, and validate it against your Laravel 10 runtime. Do not assume a PHP version from the Laravel requirement alone.
- How should I test a thyyppa/nova-json upgrade in staging?
- Create an upgrade branch, pin the currently working version, and update to v4.0.0 in a staging environment first. Run your application test suite plus Nova-specific smoke tests for resource forms, JSON editing, validation, and admin UI behavior. Compare published config and assets, then deploy with a rollback plan and monitor Nova admin paths.
- What are the alternatives to thyyppa/nova-json for editing JSON in Laravel Nova?
- The provided assessment does not name specific alternative packages. Evaluate other Nova JSON or key-value field packages, plus the built-in Nova field options available in your version, against your Laravel and Nova compatibility needs. Compare maintenance activity, field-spreading behavior, validation support, and upgrade risk before switching.
- Is thyyppa/nova-json actively maintained and what support can I expect?
- The v4.0.0 release aligns the package with Laravel 10 and Nova 4, which is positive for long-term maintenance and avoids relying on end-of-life framework lines. However, the release note alone does not clarify issue triage, security response, upgrade guides, or a published support window. If the package is critical to admin operations, confirm those support expectations with the maintainer before production rollout.