Weave Code
Foundation Bundle Laravel Package
modera/foundation-bundle
Modera Foundation Bundle provides shared base services, utilities, and integration helpers for Modera-based PHP applications. It gives other bundles a consistent foundation for configuration, common functionality, and extension.
[READ-ONLY] Bundle ships some very basic utility classes.
Frequently asked questions about Foundation Bundle
- Is modera/foundation-bundle a Laravel package?
- No. Despite often being filed under Laravel/PHP packages, modera/foundation-bundle is a Symfony bundle (ModeraFoundationBundle). It integrates through Symfony's HttpKernel and DependencyInjection contracts: a Bundle subclass, a DI extension that merges a Configuration tree, compiler passes, and XML/YAML service definitions. Laravel has no equivalent lifecycle, so installation and configuration do not translate.
- Can I install modera/foundation-bundle in Laravel 10 or 11?
- Almost certainly not cleanly. A modern Laravel baseline pins illuminate/* components and PHP 8.1+, while the bundle's transitive graph dates from 2016 Symfony and Doctrine releases. Expect composer require to fail on constraint resolution before you ever reach a runtime error. Making it work would mean building an adapter or fork, which changes the cost from install-and-configure to re-host.
- Why does composer require modera/foundation-bundle fail on dependency resolution?
- The package's last release was 2016-06-10, so its composer.json pins PHP, Symfony, and Doctrine versions from that period. Those constraints conflict with the illuminate/* set and the PHP 8.1+ floor of a modern Laravel application. Composer 2 resolves strictly, so you get a conflict report rather than an install.
- What Laravel version does modera/foundation-bundle support?
- None officially. It is a Symfony 2.x/3.x-era bundle and predates Laravel 5.4, let alone Laravel 10 or 11. There is no Laravel service provider, facade, or config publishing in the package. Any Laravel use would require you to write the provider and configuration layer yourself.
- Is modera/foundation-bundle maintained or abandoned?
- Effectively abandoned. The last release was on 2016-06-10, roughly nine years without a security patch, PHP 8 compatibility fix, or dependency refresh. It has about 2 stars and 0 dependents, so there is no community or downstream project exercising the code paths you would rely on. You would inherit any future CVEs in the transitive tree with no upstream to defer to.
- What alternatives should I use instead of modera/foundation-bundle for a Laravel app?
- For Laravel, use first-party components (laravel/framework, illuminate/support) plus small, maintained packages such as spatie/laravel-package-tools or standalone symfony/* components. If you only want domain ideas, read the Modera source as a pattern reference and reimplement in-house against Laravel idioms. That costs hours and carries no dependency risk.
- Does modera/foundation-bundle work on PHP 8.1 and PHP 8.2?
- Not without patching. Code of that vintage commonly hits removed each(), curly-brace string offsets, create_function, dynamic property deprecations in 8.2, and Serializable/Countable signature changes. Each of those is a fork-and-patch, not a config change. Expect to maintain your own fork if you depend on it.
- How do I test modera/foundation-bundle in a Laravel application?
- There is no meaningful test suite to lean on, so you would have to write your own characterization tests around any class you extract. You cannot exercise the bundle lifecycle in Laravel because there is no bundle registration, config-tree merge, or compiler pass. Treat any spike as a per-class port with your own PHPUnit coverage, not an integration test of the package.
- Can I use individual classes from ModeraFoundationBundle in Laravel?
- Sometimes, technically. The Composer autoload (PSR-0/PSR-4) will resolve, so standalone value objects or utilities can be imported. But the bundle exists to provide the Symfony wiring layer that Laravel cannot use, so the value is per-class, not per-package, and each class must be re-hosted behind a Laravel service provider. Check for hard require edges to sibling modera/* packages before copying anything.
- What are the production risks of using modera/foundation-bundle?
- Three ranked risks: abandonment (no security patches since 2016), zero adoption signal (2 stars, 0 dependents, no community write-ups), and runtime incompatibility with PHP 8.x. There is also licensing exposure: Modera's foundation stack was oriented around Sencha ExtJS admin tooling, and ExtJS carries GPLv3-or-commercial terms, so verify whether any Sencha assets are bundled or implied. Treat that as a procurement and legal question before an engineering one.
Weaver
How can I help you explore Laravel packages today?