- What is survos/kit-bundle used for?
- It provides base classes and traits for bundle development that auto-register routes, commands, Twig namespaces, and AssetMapper paths by convention. The package also bundles a reusable application kit with Twig components, Stimulus controllers, shared services, and configuration defaults for data-driven admin interfaces. The repository describes Symfony 8.1 bundle development, while the technical assessment evaluates it as a Composer PHP package for Laravel-style service provider registration.
- How do I install survos/kit-bundle with Composer?
- Install it with composer require survos/kit-bundle and ensure your runtime meets the hard PHP 8.1 minimum asserted in version 2.0.1. Register the package through the standard framework mechanism, such as a Laravel service provider with auto-discovery or a Symfony bundle entry. The provided context does not include exact installation snippets, so confirm service provider or bundle registration against the source before shipping.
- Does survos/kit-bundle support Laravel, or is it Symfony-only?
- The repository overview describes Symfony 8.1 bundle base classes, but the technical evaluation frames it as a Laravel/PHP package consumed via Composer and registered through a service provider. The provided metadata does not prove a tested Laravel support matrix or Laravel-specific integration details. Treat Laravel support as unverified until you confirm service provider behavior, configuration publishing, and CI coverage in a staging application.
- What PHP version does survos/kit-bundle require?
- Version 2.0.1 asserts a hard PHP 8.1 minimum, and the release note states that you really need 8.1. The 2.0.0 metadata may have understated the true platform floor, so treat 2.0.0 as unsafe on PHP 8.0 regardless of what it claimed. Applications on PHP 8.1 or newer fit the stated constraint, while PHP 8.0 and older will fail Composer resolution.
- Why did 2.0.1 change the PHP requirement in a patch release?
- The release note is extremely terse and appears to correct the platform floor to PHP 8.1, which is unusual for a patch release. If 2.0.0 allowed PHP 8.0 in composer.json, consumers may have passed dependency resolution and then hit runtime fatals from 8.1-only language features. The notes do not clarify whether any code changed, so review the diff and pin versions deliberately.
- Which Laravel versions are supported by survos/kit-bundle?
- The provided assessment does not include an evidence-backed Laravel support matrix, and it explicitly asks for a tested CI matrix across PHP 8.1, 8.2, 8.3, and 8.4 and Laravel 9, 10, 11, and 12. The PHP 8.1 floor aligns with Laravel 10 and 11 but excludes Laravel 9 deployments running on PHP 8.0.x. Test the package against your exact Laravel and PHP combination before adopting it.
- How does convention-based auto-registration work for routes, commands, Twig namespaces, and AssetMapper paths?
- The package supplies base classes and traits that register those resources by convention instead of requiring manual configuration for every bundle. This is intended to reduce boilerplate when packaging reusable admin and UI functionality across Survos projects. The README excerpt provided does not document exact directory names, namespaces, or override rules, so inspect the source and configuration defaults before relying on the conventions.
- Is survos/kit-bundle safe for production use?
- It can be safe on PHP 8.1 or newer if your application test suite passes, but the assessment flags weak change documentation as the dominant risk. Version 2.0.0 should be treated as unsafe on PHP 8.0 because its platform constraint may have been understated. Pin exact versions, run integration tests, and monitor releases closely so security-patch triage is not delayed by terse release notes.
- What are alternatives to survos/kit-bundle for Laravel package development?
- Common Laravel alternatives include spatie/laravel-package-tools, Laravel Package Tools, and Orchestra Testbench for package service providers and testing. For Symfony-oriented bundle conventions, native Symfony bundle base classes and framework extension patterns are the closer comparison. Choose based on whether you need Laravel service provider conventions, Symfony bundle auto-registration, or both behind separate abstractions.
- How should I handle survos/kit-bundle if it is a transitive dependency?
- The assessment warns that a transitive platform constraint affects the whole Composer graph even when you cannot change the direct requirement. On PHP 8.0 this can block unrelated upgrades and surface as a dependency-resolution conflict rather than an application bug. Prefer moving the runtime to PHP 8.1 or newer instead of pinning 2.0.0 as a safe resting place, and coordinate with the maintainer of the package that pulls it in.