- Can I use this plugin in Laravel to auto-register Symfony bundles from c33s/construction-kit-bundle?
- Technically yes, but with caveats. The plugin writes a config file to `config/config/c33s_construction_kit.composer.yml`, which Laravel doesn’t natively handle. You’d need to manually load Symfony bundles via `Bundle::registerBundles()` in a Laravel event listener or wrapper service provider.
- What Laravel versions does this plugin support?
- The plugin itself doesn’t enforce Laravel version constraints, but it assumes Symfony bundle compatibility. Laravel 8+ may work if you manually bridge Symfony bundles, but test thoroughly—Laravel’s DI container won’t auto-register Symfony bundles without extra work.
- How do I disable the plugin if it’s causing issues?
- Add `"extra": { "c33s-construction-kit-disabled": true }` to your `composer.json`. This prevents the plugin from running during `composer install` or `update`. Remove it to re-enable.
- Will this plugin conflict with Laravel’s config caching?
- Yes, the plugin writes to `config/config/c33s_construction_kit.composer.yml`, which Laravel’s config cache may ignore or override. Use Laravel’s `config_cache` to merge this into a PHP config file (e.g., `config/c33s_construction_kit.php`) instead.
- Do I need c33s/construction-kit-bundle for this to work?
- Yes, this plugin is designed to work *only* with `c33s/construction-kit-bundle`. Without it, the generated config file won’t be used, and you’ll miss bundle integration features. Consider alternatives if vendor lock-in is a concern.
- How do I manually trigger the plugin’s bundle detection?
- Run `composer run-script post-update-cmd` after installing or updating packages with the `c33s-building-blocks` extra. This bypasses Composer’s automatic triggers if needed.
- Are there Laravel-native alternatives to this plugin?
- Yes. Parse the `c33s-building-blocks` extra manually in `composer.json` and register bundles via a custom Laravel service provider. Avoid Symfony-specific logic entirely by using standalone libraries (e.g., `symfony/dependency-injection`) instead of bundles.
- What happens if the plugin fails to write the config file?
- The plugin will log errors but won’t crash Composer. Check permissions for the `config/` directory and ensure `post-update-cmd` scripts aren’t blocked. As a fallback, manually create the file or disable the plugin as described above.
- Can I use this with Laravel’s package auto-discovery?
- No, this plugin is Symfony-focused and doesn’t integrate with Laravel’s package auto-discovery. You’d need to manually map Symfony bundles to Laravel service providers or use a wrapper package to bridge the gap.
- Is there a risk of breaking changes if c33s/construction-kit-bundle updates?
- Yes, the plugin depends on the bundle’s `c33s-building-blocks` extra format. Monitor updates to `c33s/construction-kit-bundle` for schema changes. Test in a staging environment before applying updates to production.