- What is richcongress/bundle-toolbox used for?
- It is a small shared utility bundle for Symfony/PHP projects that provides common helpers and conventions for building and maintaining bundles. It standardizes setup and reduces boilerplate across RichCongress packages with minimal configuration. It is aimed at bundle authors rather than application feature development.
- Does richcongress/bundle-toolbox work with Laravel?
- The package is described as a Symfony/PHP bundle, not a Laravel-specific package, so Laravel support depends on whether your application and the package Composer constraints share compatible Symfony components. Check composer.json for symfony/*, illuminate/*, and PHP requirements before assuming compatibility. Test installation in a branch or CI environment rather than adding it directly to production.
- How do I install richcongress/bundle-toolbox with Composer?
- Install it with composer require richcongress/bundle-toolbox, preferably pinned to a tested version during evaluation. Review the resulting composer.lock diff and confirm no unrelated Laravel or Symfony dependencies were upgraded. Run your application test suite immediately after installation.
- Which Symfony and PHP versions does v1.2.5 support?
- The only release note for v1.2.5 mentions Symfony 6.X, but it does not state supported PHP versions, Laravel versions, or whether Symfony 5 remains compatible. Treat it as a dependency-constraint change until you inspect composer.json and the diff. Verify the exact PHP and Symfony constraints against your production stack.
- Does v1.2.5 drop Symfony 5 support?
- The terse release note does not confirm whether Symfony 6 support was added alongside Symfony 5 or replaced it. Because this is a patch release, a constraint change could still be breaking in practice for older stacks. Inspect composer.json and run composer why-not to determine the actual supported range.
- How do I resolve Composer conflicts with richcongress/bundle-toolbox?
- Use composer why-not richcongress/bundle-toolbox to identify which Laravel, Symfony, or PHP constraint blocks installation. Avoid loosening unrelated dependencies just to force resolution. If the host application is on an older Laravel/Symfony stack, stay pinned or plan a framework upgrade first.
- How should I upgrade to v1.2.5 safely?
- Create a dedicated upgrade branch, require v1.2.5, and update only that package and its dependencies. Run unit, integration, and smoke tests, then validate in staging with production-like caches and config before a production canary. Keep the previous lockfile for rollback.
- Is richcongress/bundle-toolbox safe for production?
- Technical risk is medium until verified because the release note is sparse and the package changes dependency compatibility. There is no expected runtime scaling impact from a compatibility release, but confirm no service provider boot, cache, session, or queue behavior changed. Document tested versions and rollback steps before production use.
- Are there alternatives to richcongress/bundle-toolbox for Laravel?
- If you need Laravel package scaffolding, Laravel package discovery, service providers, and tools like Orchestra Testbench are more direct alternatives. This package is best suited to projects already using RichCongress bundle conventions or needing shared Symfony bundle helpers. Evaluate whether you need a Symfony bundle at all in a Laravel application.
- How is richcongress/bundle-toolbox maintained and tested?
- The provided assessment notes a sparse changelog and does not confirm a published CI matrix for Laravel, Symfony, and PHP versions. Maintain an internal compatibility matrix and track Composer constraints, security advisories, and deprecations. Inspect source diffs when release notes are minimal.