Weave Code
Framework Extra Bundle Laravel Package
short-edition/framework-extra-bundle
Framework Extra Bundle extends Laravel with practical helpers, traits, and utilities that reduce everyday boilerplate. With simple service provider registration, it drops convenient, reusable features into your app without restructuring existing code, helping you ship faster.
This bundle provides a way to configure your controllers with annotations
Frequently asked questions about Framework Extra Bundle
- What is short-edition/framework-extra-bundle?
- It is a fork of SensioFrameworkExtraBundle, a Symfony bundle that configures controllers with annotations such as @Route, @Template, @Cache, and @ParamConverter. It is not a Laravel package despite Laravel-oriented framing, and it depends on Symfony bundle and event-dispatcher architecture. Treat it as a legacy Symfony component snapshot, not a drop-in Laravel helper.
- Is short-edition/framework-extra-bundle compatible with Laravel?
- No. Laravel has no Symfony bundle registration, DI compiler passes, or HttpKernel event dispatcher for this bundle to hook into. You cannot meaningfully install or use it in a Laravel app. For Laravel, use native routing, route-model binding, view() inference, middleware, and Gate/Policy instead.
- Can I install short-edition/framework-extra-bundle in a Laravel 10 or 11 app?
- You might technically add it to Composer, but it will not integrate with Laravel's routing, container, or middleware. The package expects Symfony bundle conventions and annotations, so you would be carrying dead code and unnecessary dependencies. Do not plan a Laravel feature around it.
- What Symfony versions does this fork support?
- The provided context does not specify a supported Symfony version matrix. Upstream SensioFrameworkExtraBundle was not carried into Symfony 7, and its annotation features were replaced by native attributes in Symfony 5.2 through 6.3. Verify composer.json constraints and test against your exact Symfony version before considering it.
- Is short-edition/framework-extra-bundle maintained?
- There is no evidence of an active maintainer, release cadence, CI, security-response process, or consumer base for this fork. It appears to be a zero-star fork from a non-obvious publisher. Treat maintenance and security patching as your responsibility unless the publisher documents otherwise.
- Should I use this fork or the upstream sensio/framework-extra-bundle?
- In most cases, neither: upstream is retired and Symfony directs users to native attributes. If you must support a legacy Symfony 5.4 or 6.x app, prefer the documented upstream or an internally maintained fork with a clear patch history. Ask why short-edition forked it and what specific patch, if any, was applied.
- What replaces @Route, @Template, @Cache, @Security, and @ParamConverter in modern Symfony?
- Native PHP attributes replace them: #[Route], #[Template], #[Cache], #[IsGranted], and #[MapEntity], #[MapQueryParameter], or #[ValueResolver]. These are supported by Symfony core and avoid the deprecated doctrine/annotations runtime dependency. Migrate controller annotations to attributes before adopting any legacy bundle.
- What are the Laravel equivalents of FrameworkExtraBundle features?
- Use explicit routes or spatie/laravel-route-attributes for controller routing; return view() or View::first() for template inference; Cache::remember() or response caching for @Cache; Gate/Policy, authorize(), or can: middleware for @IsGranted; and route-model binding or Route::bind() for @ParamConverter. These Laravel-native features cover the same patterns without this package. You can reproduce the useful ideas in a small amount of application code.
- Is doctrine/annotations deprecated, and does that affect this package?
- Yes, doctrine/annotations is deprecated, and this bundle's annotation-driven controller configuration depends on that idiom. PHP 8 native attributes are the supported path in Symfony. Using this package locks you into a dead annotation style and creates future PHP-version compatibility risk.
- Is short-edition/framework-extra-bundle safe for production?
- Technical risk is high mainly due to provenance: an unmaintained fork of a retired upstream with no visible security process. Any CVE, PHP 8.4+ incompatibility, or doctrine/annotations issue would likely go unfixed here. For production Laravel, avoid it; for legacy Symfony, isolate it and own the patching plan.
Weaver
How can I help you explore Laravel packages today?