Weave Code
Mvc Bundle Laravel Package
gyro/mvc-bundle
Gyro MVC Bundle provides a lightweight MVC layer for Gyro applications, adding routing, controllers, action handling, and view rendering. It helps organize PHP projects into clean models, views, and controllers with a bundle-based architecture.
Gyro MVC Bundle is a lightweight PHP package that adds a clean Model-View-Controller structure to your application. It provides conventions for organizing controllers, routing requests, and rendering views, helping separate application logic from presentation and making projects easier to navigate and extend.
- MVC scaffolding for controllers, actions, and views
- Flexible routing with clear request-to-controller mapping
- View rendering with template support
- Configuration-driven setup for straightforward integration
- PSR-friendly structure for modern PHP workflows
Frequently asked questions about Mvc Bundle
- Is gyro/mvc-bundle compatible with Laravel?
- No. It is a Symfony bundle built on Symfony's HttpKernel, DependencyInjection, EventDispatcher, and Routing components. Laravel does not expose those contracts, so there is no supported installation path. You would need to boot a Symfony kernel alongside Laravel, which is rewrite-scale work rather than an integration.
- How do I install gyro/mvc-bundle?
- Composer installation is trivial with composer require gyro/mvc-bundle. In a Symfony application you then register the bundle in config/bundles.php. In Laravel it will not register because there is no bundle system. Confirm the PHP and Symfony constraints in composer.json before installing.
- Which Symfony and PHP versions does gyro/mvc-bundle support?
- Check composer.json for the PHP floor and Symfony component constraints. The assessment notes a 2025-03-23 release but does not list exact supported versions. Pin exact versions and validate against your supported Symfony LTS only. Do not assume a broad version matrix for a package with no external users.
- Does gyro/mvc-bundle require other gyro packages?
- Likely yes. It is part of the Gyro CMF/CMS project and probably depends on sibling gyro/* packages. Adopting one package can pull in a cluster, so inspect the transitive footprint in composer.json. Confirm the maintenance status of each dependency before committing.
- Is gyro/mvc-bundle actively maintained?
- It is a single-organization project with minimal external contribution. A release on 2025-03-23 indicates recent activity but not community depth. At 16 stars and 0 dependents there is no public reference implementation or observable production usage to learn from. Treat abandonment and bus factor as high risks.
- What are the alternatives to gyro/mvc-bundle for Symfony?
- Symfony first-party features cover most needs: #[Route] attributes, AbstractController, MapRequestPayload, and #[Template]. These are maintained by Symfony and well documented. For Laravel, use invokable controllers, route-model binding, FormRequests, API Resources, or spatie/laravel-route-attributes. Confirm the specific problem you need solved before adopting a third-party bundle.
- Can I migrate a Laravel app to gyro/mvc-bundle?
- No. There is no migration path from Laravel and no partial-install story. The bundle targets Symfony's kernel and DI contracts, which Laravel does not provide. If you run Symfony services, treat it as a greenfield spike in a throwaway branch, not a migration.
- What is the license and test coverage for gyro/mvc-bundle?
- The assessment does not state the license or test coverage, so check the repository LICENSE and test suite. Confirm the tests are runnable and meaningfully cover controllers, routing, and view resolution. A tiny install base means vulnerabilities and regressions are more likely to be found by you than upstream.
- What are the production risks of using gyro/mvc-bundle?
- Risks include bus factor, coupling to sibling gyro packages, semantic drift from monorepo-style releases, and an upgrade ceiling if the bundle becomes unmaintained. There is no security advisory history or disclosure process, and the install base is tiny. Pin exact versions and validate only against your supported Symfony LTS.
- What problem does gyro/mvc-bundle solve and should I adopt it?
- It wires routing, controllers, and view rendering with minimal configuration for Gyro applications. Before adopting, name the concrete pain you are solving, such as controller boilerplate or attribute routing. If the target is Laravel, do not adopt because there is no bridge worth building. If the target is Symfony, evaluate only the specific improvements you need and confirm no first-party equivalent exists.
Weaver
How can I help you explore Laravel packages today?