- Is nova-kit/nova-packages-tool still maintained or recommended for Laravel Nova package development?
- No, this package is deprecated. Its functionality has been fully replaced by **laravel/nova-devtool**, which is the official and recommended tool for Laravel Nova package development. Migrate to avoid compatibility risks.
- What are the key differences between nova-kit/nova-packages-tool and laravel/nova-devtool?
- laravel/nova-devtool is the official successor, offering updated Laravel 13+ support, tighter Nova integration, and modernized tooling. It eliminates legacy dependencies and aligns with Laravel’s latest security and performance standards.
- Can I still use nova-kit/nova-packages-tool with Laravel 13?
- Technically yes, but it’s not recommended. The package supports Laravel 13, but it lacks official updates and may conflict with Nova’s latest features. Use **laravel/nova-devtool** instead for guaranteed compatibility.
- How do I migrate from nova-kit/nova-packages-tool to laravel/nova-devtool?
- Uninstall nova-kit/nova-packages-tool via Composer, then install laravel/nova-devtool. Review the [nova-devtool migration guide](https://github.com/laravel/nova-devtool) for updated commands and configuration changes.
- Does nova-kit/nova-packages-tool support Nova 5.0+?
- No, this package is outdated and may not fully support Nova 5.0+. laravel/nova-devtool is actively maintained and explicitly tested against Nova’s latest versions, including 5.0+.
- Will nova-kit/nova-packages-tool break my existing Nova package if I upgrade Laravel to 13?
- Possible, but unlikely. However, since it’s deprecated, there’s no guarantee of compatibility with Laravel 13’s updated APIs. Switch to laravel/nova-devtool to avoid risks like facade or dependency conflicts.
- Can I use nova-kit/nova-packages-tool for testing custom Nova fields or tools?
- Yes, but it’s not ideal. The package provides basic testing utilities, but laravel/nova-devtool offers more robust tools, including pre-configured test environments and Laravel 13-specific validation.
- Are there any security risks using nova-kit/nova-packages-tool in production?
- Potential risks include outdated dependency handling and lack of updates for Laravel 13’s security patches. laravel/nova-devtool addresses these concerns with modern security practices and active maintenance.
- What alternatives exist if I can’t use laravel/nova-devtool?
- For now, laravel/nova-devtool is the only official alternative. If you’re locked into an older Laravel/Nova version, consider forking this package or manually implementing its core features (e.g., tool registration, field overrides).
- How do I check if my Nova package is compatible with Laravel 13 before migrating tools?
- Run `php artisan vendor:publish --tag=nova-assets` and test in a fresh Laravel 13 environment. Check for deprecation warnings in `storage/logs/laravel.log` and validate Nova’s asset pipeline (Vite/Inertia) for conflicts.