- Is scylabs/hook-bundle compatible with Laravel?
- No. scylabs/hook-bundle is a Symfony bundle, not a Laravel package. It ships a ScyLabsHookBundle class, a DependencyInjection extension, and service-container wiring that only resolves inside a Symfony Kernel. Composer will install it in a Laravel app, but no service provider, facade, or auto-discovery entry exists, so nothing registers.
- How do I install scylabs/hook-bundle in a Laravel application?
- You can run composer require scylabs/hook-bundle, but installation alone will not make it work in Laravel. There is no Laravel service provider or package manifest entry to discover, so the bundle's hooks never boot. Using it would require a hand-written adapter or fork, and the template-hook semantics would have to be reimplemented in Blade anyway.
- What is scylabs/hook-bundle used for?
- It provides a lightweight hook system for PHP applications, letting you register callbacks against named hooks and dispatch them at defined points. Callbacks can be ordered by priority and receive contextual arguments, so packages and application code can extend behavior without tight coupling. In practice it is a Symfony convention layer for injectable template fragments at named positions.
- Can I use scylabs/hook-bundle hooks in Laravel Blade views?
- Not directly. The package's model is built around Symfony bundle configuration and template injection points, not Blade. Wrapping its Symfony container extension into Laravel's service container would mean reimplementing the hook semantics in the view layer, which is a rewrite rather than an integration. For Blade, use Laravel view composers, Blade components, or event/listener patterns instead.
- Which Laravel versions does scylabs/hook-bundle support?
- None are stated or supported. The package is a Symfony bundle and does not publish a Laravel version matrix. There is also no evidence in v1.0.6 of widened php, symfony, or twig constraints, so do not infer Symfony 6/7 or Twig 3 support from the patch release.
- How do I configure scylabs/hook-bundle?
- Configuration is handled through Symfony bundle config and the bundle's DependencyInjection extension. In a Symfony Kernel you register the bundle and define its service-container wiring; there is no Laravel config file, service provider, or facade. v1.0.6 specifically fixes container injection in that Symfony DI path.
- What changed in scylabs/hook-bundle v1.0.6?
- The release note says "Fixes Container injection," which is a patch to the Symfony DI extension that must work for the bundle to boot at all. That is a favorable signal that the maintainer is not entirely absent. It does not, however, document which Symfony versions are fixed, widen compatibility constraints, or add a changelog or CI.
- Is scylabs/hook-bundle actively maintained?
- Barely. v1.0.6 is a single patch after roughly a five-year gap, which shows responsiveness but is not a support commitment. There is no visible governance, security policy, issue triage, changelog, test suite, or CI. Treat abandoned-upstream risk as medium and revert to high if no follow-up activity appears.
- What are Laravel alternatives to scylabs/hook-bundle?
- For Laravel, use native events and listeners, service providers, view composers, Blade components, or custom pipeline/middleware patterns. These are framework-native, tested, and supported. On Symfony, the equivalent ground is covered by EventDispatcher subscribers and Twig runtime extensions rather than this bundle.
- Is scylabs/hook-bundle safe for production?
- Use caution. It is MIT-licensed with a small surface area, but it is a Symfony-only bundle with no Laravel integration, no test or CI evidence, and no known dependents. Hook registration failures tend to degrade gracefully by missing content rather than throwing, so verify behavior in a throwaway app before considering production.