- Is qce/core-bundle a Laravel package or a Symfony bundle?
- The package overview describes it as a shared foundation for Laravel/PHP applications, including Laravel auto-discovery and publishable configuration. However, the Composer name qce/core-bundle and the QceCoreBundle suffix are Symfony-style signals, so the framework target should be confirmed by reading the source and composer.json before adoption.
- How do I install qce/core-bundle in a Laravel application?
- Installation would normally be done with Composer using the package name qce/core-bundle. Before running it, confirm the package is available from Packagist and that any sibling QCE dependencies are published, because the bundle may not be installable on its own. Also verify whether the package actually targets Laravel, since the naming suggests a Symfony bundle.
- Does qce/core-bundle support Laravel auto-discovery for its service providers?
- The overview says modular service providers are registered via Laravel auto-discovery, which would use the extra.laravel.providers entry in composer.json. That claim should be checked in the actual composer.json, especially because the bundle-style naming raises questions about whether it is Laravel-native or Symfony-shaped.
- How do I publish the QCE Core Bundle configuration file?
- The package is described as having publishable configuration with sensible defaults, so the expected Laravel workflow is to publish the config with an artisan vendor:publish command after installation. The exact publish tag or config file name is not provided in the available context, so confirm it from the package source or README before relying on it.
- What Laravel and PHP versions does qce/core-bundle support?
- The provided context does not list specific Laravel, PHP, Symfony, or illuminate/* version constraints. Because the package has no documented releases or changelog in the available information, you should inspect composer.json and test against your pinned framework version before adoption. A major-version gap would be a hard stop for a core dependency.
- Does qce/core-bundle depend on other QCE packages?
- The overview describes reusable helpers and contracts shared across QCE packages, which suggests it may be coupled to sibling QCE packages. The available context does not confirm which siblings exist or whether they are published on Packagist. Check composer.json require and require-dev sections and verify every dependency is installable.
- Can I use qce/core-bundle in production if it has no releases or changelog?
- The assessment notes no observable release cadence, changelog, stars, dependents, or documented consumers, so there is no visible stability contract. Production use would require a source audit, a pinned commit or version, and your own test coverage. Treat it as evaluating an internal component rather than procuring a maintained product.
- How do I test a Laravel app that uses qce/core-bundle?
- There is no test suite or CI evidence described in the provided context, so you should add your own integration tests around the service providers and published configuration. Test container bindings, config defaults, and any helpers or contracts the bundle exposes, and pin the dependency version you audit. If the package is Symfony-shaped, a Laravel test harness may not exercise it correctly.
- What are alternatives to qce/core-bundle for sharing common Laravel package foundations?
- For Laravel-only reuse, teams often use a private Composer package or a monorepo with shared service providers, config defaults, and contracts rather than a core bundle. Laravel package conventions such as auto-discovery and vendor:publish are well documented, and an internal package gives you control over versioning and release cadence. The right alternative depends on whether the QCE ecosystem already requires this specific bundle.
- Is qce/core-bundle actively maintained and open to contributions?
- The available context shows no release cadence, changelog, dependents, or documented consumers, and the vendor appears to have extracted an internal component for its own reuse. The MIT license keeps legal friction low and allows forking, but it does not guarantee issue responses or external PR acceptance. Confirm maintenance expectations with the vendor before making it a core standard.