Weave Code
Framework Bundle Laravel Package
fusonic/framework-bundle
A Symfony framework bundle from Fusonic that bundles shared framework utilities and integrations to speed up application setup. Small and lightweight, it is best suited to projects already within the Fusonic ecosystem; documentation and community adoption are limited.
Opinionated collection of classes and functionalities used throughout @fusonic's Symfony projects
Frequently asked questions about Framework Bundle
- Can I use fusonic/framework-bundle in a Laravel application?
- No, not directly. It is a Symfony bundle whose integration contract is Symfony's Bundle class, DependencyInjection Extension::load(), compiler passes, and YAML config trees under config/packages. Laravel bootstraps through ServiceProviders, the Illuminate container, and config/*.php files, so any service defined by Symfony service ID, tag, or ContainerInterface will not resolve without a translation layer. Writing that adapter would cost more than the utility code it wraps.
- What is fusonic/framework-bundle actually used for?
- It is an opinionated collection of classes and integrations that Fusonic reuses across its own Symfony projects, likely covering base entity and aggregate types, Doctrine repository helpers, security helpers, and validation or serialization glue. It is not a narrow, framework-agnostic utility library with a documented public API. Its value is concentrated inside the Fusonic ecosystem and its internal project conventions.
- How do I install and configure fusonic/framework-bundle?
- In a Symfony app you would run composer require fusonic/framework-bundle, register it in config/bundles.php, and add any bundle configuration under config/packages/. There is no Laravel service provider or config file to publish, so the standard composer require step does not get you a working setup in Laravel. Expect PHP ^8.2 and Symfony 6.4 or 7.x constraints, so verify them in composer.json before attempting anything.
- Does fusonic/framework-bundle support Laravel 10, 11, or 12?
- There is no official Laravel support, and given the bundle's structure none should be expected. The package targets Symfony's kernel and container; Laravel version numbers are irrelevant to its compatibility matrix. Installing it in a Laravel project will at best leave the bundle's services unregistered and at worst pull in conflicting Symfony HTTP kernel or security dependencies.
- Which PHP, Symfony, and Doctrine versions does fusonic/framework-bundle require?
- Expect tight pins such as PHP ^8.2 and symfony/* ^6.4 || ^7.0, and likely doctrine/orm as either a direct or transitive dependency. These constraints are the first thing to check in composer.json, because any drift from your PHP baseline blocks installation outright. Because the bundle has almost no downstream consumers, those pins may also lag or jump without notice between tags.
- Is fusonic/framework-bundle actively maintained?
- Signals are weak: roughly one star, no visible dependents, and a description that reads as code extracted from internal projects. With no downstream consumption there are no bug reports, no compatibility pull requests, and no early warning when a Symfony major release changes a signature. Treat release cadence and support commitments as unproven until the maintainers document them.
- Does fusonic/framework-bundle require Doctrine, and can it coexist with Eloquent?
- It very likely depends on Doctrine ORM, since base entity, aggregate, and repository classes are typical of bundles of this kind. Running Doctrine alongside Eloquent means maintaining two persistence abstractions and two connection lifecycles in one application. That overhead is hard to justify for a small utility bundle, so confirm the dependency list before considering it.
- Can I cherry-pick individual classes from fusonic/framework-bundle without Symfony DI?
- Yes, and this is the more realistic path. Identify the specific value objects, DTO base types, or string and date helpers you need, copy them into app/Support or a first-party internal package, and strip any Symfony container expectations such as autowiring by service ID or tagged services. The MIT license permits this as long as you keep the copyright notice and attribution in your README or NOTICE file. You then own the code and are insulated from upstream churn.
- What are good alternatives to fusonic/framework-bundle for a Laravel project?
- For most of what this bundle offers, Laravel's own helpers, collections, and Eloquent cover the ground, and packages like spatie/laravel-data or symfony/string fill in DTO and string utility gaps. If you need a specific Symfony component such as the validator or serializer, install that component alone rather than a whole opinionated bundle. Framework-agnostic, well-adopted Composer packages will always be a lower-risk choice than a single-maintainer bundle with no dependents.
- Is fusonic/framework-bundle safe to run in production?
- There is unquantified supply-chain risk. Bundles that register services and security helpers touch dependency injection and authentication configuration, and this one has a single maintainer with no visible security disclosure policy and no downstream consumers to surface issues. The safest production stance is not to install it and instead vendor any genuinely useful classes under MIT attribution with your own review and tests.
Weaver
How can I help you explore Laravel packages today?