- Is kingfoo/framework-bundle a Laravel package?
- No. It is a Symfony bundle with Composer type symfony-bundle, and its integration points are Symfony's kernel bundle registry, dependency injection extension, and config tree. Laravel has no bundle contract; it uses service providers and the Illuminate container. There is no adapter in the package for Laravel bootstrapping.
- Can I install a Symfony bundle in a Laravel application?
- You can add the Composer dependency, but it will not wire into Laravel's boot cycle. The bundle expects Symfony kernel or config/bundles.php registration and Symfony's DependencyInjection extension model. In Laravel it would be dormant at best, and it may create dependency conflicts. There is no install, register, configure sequence that makes it functional.
- Is kingfoo/framework-bundle deprecated?
- Yes. The package description explicitly says [DEPRECATED] use symfony/framework-bundle instead. That is the maintainers pointing adopters to Symfony's first-party bundle. Deprecation means no new features, bug fixes, or security response.
- What should I use instead of kingfoo/framework-bundle in Laravel?
- For Laravel, use Laravel-native features and illuminate components rather than a Symfony bundle. Service providers, config publishing, facades, and the container cover the bootstrapping and configuration needs described here. If the target is actually Symfony, use symfony/framework-bundle as the deprecation notice advises.
- Does kingfoo/framework-bundle support Laravel 10 or Laravel 11?
- There is no Laravel version support to claim because the package is not a Laravel package. It targets Symfony's bundle system and has no Illuminate service provider, facade, or config publishing integration. Its unmaintained Composer constraints are also unlikely to resolve cleanly against modern Laravel dependency trees.
- How do I install kingfoo/framework-bundle?
- It would be installed with Composer and PSR-4 autoloading, but installation alone does not integrate it with Laravel. In Symfony you would register the bundle in the kernel or bundles.php and expose options through the config tree. For a Laravel app, installation is not recommended because there is no functional integration path.
- Why does Composer fail when I add kingfoo/framework-bundle to Laravel?
- The bundle carries Symfony-era dependency constraints that may conflict with modern PHP and Symfony component versions in a Laravel lock file. Composer may fail resolution or pin other packages backward to satisfy it. That is a dependency-graph risk, not a local install issue.
- Is kingfoo/framework-bundle safe for production?
- No. It is self-declared deprecated, unmaintained, and has no meaningful adoption signal such as stars or dependents. Deprecated packages do not receive security or compatibility fixes, and the Symfony bundle contract does not run in Laravel. Production use would add risk without delivering the intended integration.
- What are Laravel alternatives to this Symfony bundle's features?
- Laravel already provides service providers for registration, config files and publishing for options, and the Illuminate container for dependency injection. Use those first-party mechanisms instead of trying to port a Symfony extension and compiler pass model. For Symfony applications, symfony/framework-bundle is the named replacement.
- How do I remove kingfoo/framework-bundle from an existing project?
- Remove the Composer requirement and delete the bundle registration line from the Symfony kernel or config/bundles.php. Inline any defaults the bundle registered into config/packages/*.yaml, then run Composer update and your test suite. If the project is Laravel, remove it entirely and re-derive the requirement using Laravel-native features.