Weave Code
Controller Bundle Laravel Package
imatic/controller-bundle
imatic/controller-bundle is a Laravel/PHP package that provides controller-focused utilities for organizing actions and streamlining common controller patterns. It aims to reduce boilerplate and keep controller code structured, making standard request-handling flows easier to build and maintain.
Bundle to write simple controllers
Frequently asked questions about Controller Bundle
- Is imatic/controller-bundle a Laravel package?
- No. It is a Symfony bundle that ships an abstract base controller with helpers for responses, redirects, flash messages, sessions, and container lookups. It has no service provider, facade, config file, or any Laravel-tested code path. The Laravel framing in some package summaries is inaccurate.
- What does imatic/controller-bundle actually do?
- It provides a reusable base controller class that your Symfony controllers extend instead of Symfony's own AbstractController. From there you get shortcut methods for JSON, redirect, and file responses, flash message and session access, and quick retrieval of services and parameters from the container. The goal is simply less repeated response-building code in action methods.
- Can I install imatic/controller-bundle in a Laravel application?
- Composer may resolve it, but nothing in the package targets Laravel. Its framework version constraints reference Symfony components, so requiring it can pull Symfony packages into your dependency graph for a helper class you can write in about twenty lines. Run composer why before approving it, and reject the install if Symfony components appear.
- How do I install and register imatic/controller-bundle in Symfony?
- Require it with Composer, then register the bundle in config/bundles.php for the environments you need. After that, extend the bundle's base controller in your own controllers and start calling the response, redirect, and service helpers. Verify the declared PHP and Symfony constraints against your pinned versions first, since there is no published CI matrix proving compatibility.
- What are the Laravel equivalents of the helpers this bundle provides?
- Laravel ships all of them natively: response()->json() for JSON payloads, redirect() and back() for redirects, response()->download() and response()->file() for file responses, session()->flash() for flash messages, and app() or config() for container and configuration lookups. Illuminate\Routing\Controller already resolves dependencies from the container without any manifest. The mapping is effectively one to one.
- Which Laravel versions does imatic/controller-bundle support?
- None officially. The package declares Symfony framework constraints, not illuminate/support or illuminate/routing requirements, and it is not tested against any Laravel release. There is no supported version matrix for Laravel at all. Treat any Laravel usage as unsupported.
- Is imatic/controller-bundle actively maintained and safe for production?
- The public signals are thin: roughly one star, zero dependents, a single-maintainer namespace, and no visible CI matrix or security response process. That is the profile of an internal utility bundle rather than a maintained dependency. The MIT license is the one clean signal, since it lets you fork if you ever truly need to, but nothing here justifies that effort for a Laravel project.
- How do I test controllers that extend the bundle's base controller?
- On the Symfony side, functional tests using the KernelBrowser against a booted kernel are the practical route, plus unit tests around your own action methods. Because the package is not Laravel-aware, there are no Laravel testing hooks, factories, or helpers to lean on. Keep your controllers thin and push logic into services so most of your tests never touch the base controller.
- What are the alternatives to imatic/controller-bundle for Laravel developers?
- Native Laravel controllers are the alternative, and they already cover the full feature set. Use invokable single-action controllers, Route::controller() for grouping, form requests for validation, API resources for response shaping, and the response() and redirect() helpers. No third-party base controller is needed to reduce boilerplate in Laravel.
- How do I remove imatic/controller-bundle from a Laravel project?
- Run composer remove imatic/controller-bundle, then change any controller extending the bundle class to extend Illuminate\Routing\Controller instead. Replace each helper call with its Laravel equivalent such as response()->json(), redirect(), view(), or session()->flash(). The work is measured in hours, not sprints, and composer why will confirm whether any Symfony packages were dragged in and should also be dropped.
Weaver
How can I help you explore Laravel packages today?