- Is svc/log-bundle a Laravel package?
- No. The -bundle suffix, svc vendor namespace, and DI Extension pattern indicate it is a Symfony bundle, not a Laravel package. It has no Laravel ServiceProvider, package auto-discovery, Eloquent models, or publishable config/logging.php. Using it in Laravel requires a thin adapter and custom service provider registration.
- How do I install svc/log-bundle in a Laravel application?
- You would start with composer require svc/log-bundle, but inspect its composer.json first for symfony/framework-bundle and doctrine dependencies. Laravel already pins several Symfony components, so a bundle with incompatible ranges can fail Composer resolution. Plan for a small Laravel service provider that binds an internal logging interface to an adapter over the bundle.
- Does svc/log-bundle support Laravel 10 and Laravel 11?
- There is no native Laravel support or Laravel-specific testing evident in the package. Compatibility depends on its PHP ceiling and Symfony/Doctrine constraints against your Laravel version's resolved dependencies. Run composer why-not against your lock file before assuming Laravel 10 or 11 compatibility.
- What PHP and Symfony versions does svc/log-bundle require?
- You need to inspect the package composer.json, because the repository context does not publish a verified compatibility matrix. Look for symfony/framework-bundle constraints, a PHP upper bound, and any doctrine ORM or DBAL requirements. Those constraints determine whether it can coexist with your Laravel application's locked Symfony components.
- Can I use svc/log-bundle without Doctrine ORM?
- It depends on how the write path is implemented. If logging persists through Doctrine entities and repositories, carrying the full ORM into Laravel is a poor fit; doctrine/dbal alone is far cheaper if it is sufficient. If the database connection is hardcoded to a Doctrine entity manager, expect to fork or wrap the write path instead.
- How does svc/log-bundle handle log levels and handlers?
- The package is described as PSR-3 compatible with support for multiple handlers and configurable log levels. In Laravel, you should wire those handlers through your adapter rather than expecting config/logging.php to discover the bundle automatically. Verify the actual handler interfaces and configuration format in source before relying on them.
- Is svc/log-bundle production-ready for a Laravel app?
- Community validation is very low: two stars, zero dependents, a single maintainer, and a package score near 0.01. There is no evidence of test coverage, CI, tagged releases, issue responsiveness, or a security disclosure process. The MIT license is permissive, but treat this as code you are acquiring ownership of rather than a supported dependency.
- How should I test svc/log-bundle in a Laravel application?
- Define an internal interface such as EventRecorder or AnalyticsLogger, implement it with a thin adapter over the package, and test the adapter rather than controllers. Use a fake or in-memory handler for unit tests and add integration tests for the database write path. Since the package shows no obvious test coverage, your own tests are the safety net.
- What are alternatives to svc/log-bundle for Laravel logging?
- Laravel's built-in Monolog-based logging already provides PSR-3 channels, handlers, levels, and rotation with framework support. For database event or analytics logging, a small custom logger or a maintained Laravel package avoids Symfony/Doctrine integration friction. Alternatives also reduce the single-maintainer and bus-factor risk.
- How do I handle svc/log-bundle migrations and database configuration in Laravel?
- First confirm whether schema or migrations ship with the package and for which migration tool; a Symfony bundle likely assumes Doctrine migrations rather than Laravel migrations. Own the table schema as a first-class Laravel migration with explicit indexes and a retention or rollup plan. Also verify the database connection is injectable and not hardcoded to a Doctrine connection.