- Is akyos/core-bundle a Composer package for Laravel or for Symfony?
- It is a Symfony bundle, not a Laravel package. There is no Laravel ServiceProvider, no package auto-discovery and no publishable Laravel config. It registers through Symfony's kernel bundle list and binds to Symfony container configuration, Twig, Webpack Encore and HttpFoundation. Treat any Laravel evaluation of it as a pattern reference rather than a dependency decision.
- Can I install akyos/core-bundle in a Laravel application?
- You should not. The bundle has no Laravel integration layer, so Composer may resolve the package but none of its Twig, security, asset or pagination wiring will activate in a Laravel app. Even if you force it in, you would be carrying Symfony framework dependencies and an @dev-flagged recaptcha bundle for no functional gain. Extract the patterns instead of adopting the package.
- What PHP and Symfony versions does akyos/core-bundle require?
- The bundle requires PHP 8.4 or higher and Symfony ^8.0. That excludes most currently deployed Laravel and Symfony estates. The version line is anchored to the Symfony major, so 8.x of the bundle pairs with Symfony 8. Symfony 6.4 and 7.x projects are untested against this line.
- How do I install and register akyos/core-bundle?
- Install it with composer require akyos/core-bundle:^8.0. Because it is a Symfony bundle, you then register it in your Symfony application's bundle configuration (config/bundles.php) so the container picks up its service definitions and prepended configuration. Verify your PHP runtime is 8.4+ and that the project is on Symfony 8 before attempting install.
- What does CoreBundle actually give me out of the box?
- It ships a prebuilt bootstrap for AkyosCMS projects: configuration for Twig, assets, security, CKEditor and pagination, plus shared helpers and utilities, common entities, and mail and SMS sending services. The goal is avoiding the same bootstrap work on every new project. Most of it is configuration glue rather than a novel abstraction over Symfony.
- Which version of akyos/core-bundle should I pin on a Symfony 8 service?
- Pin ^8.0.2 at minimum. Version 8.0.2 fixed a real upstream break that caused an UndefinedMethodError when editing screens in the admin builder, but the fix was reactive: the regression shipped first. That is a reminder to smoke-test admin builder edit flows end to end after every update, not just to check the changelog.
- What are the Laravel-native alternatives to CoreBundle's features?
- Almost every capability has a first-class Laravel equivalent: league/csv for CSV ergonomics, Laravel's built-in paginator, spatie/laravel-recaptcha for captchas, Laravel's Mail and notification system for email, and Filament or Nova for admin UI. The only arguably differentiated asset is the admin builder editing UI. If that is what you need, compare Filament or Nova against running a small Symfony 8 microservice before paying dual-stack operational cost.
- Is akyos/core-bundle production-safe, and how is it maintained?
- Treat it as high risk for adoption as a dependency and low risk as a reference. It has zero stars, zero dependents, no public issue backlog and single-vendor maintenance by akyoscommunication, so there is no community to validate patch releases. The version line is tied to the Symfony major, meaning every Symfony major becomes a forced bundle major, and the @dev-flagged karser/karser-recaptcha3-bundle dependency is its own supply-chain concern. If you adopt, define who owns the upgrade cadence and keep a fork-and-own contingency.
- Does the Symfony 8 Request::get() removal affect my Laravel code even if I skip this bundle?
- Yes, and this is the one action item that applies regardless of adoption. Illuminate\Http\Request extends Symfony\Component\HttpFoundation\Request, so Symfony 8 dropping Request::get() is a latent liability inside Laravel codebases too. Grep for ->get( call sites on request objects and migrate them to $request->query->get() or $request->input() before any symfony/http-foundation major bump.
- What is the exit cost if I adopt CoreBundle and later rip it out?
- High. There is no abstraction layer over the framework contracts, so every entity, Twig template and admin screen that leaned on the bundle has to be touched. With no community and no dependents there is also no third-party migration path to lean on. That exit cost is a strong argument for extracting the pieces you need at the start rather than installing the bundle.