Weave Code
Common Bundle Laravel Package
elasticms/common-bundle
Shared code library for the elasticMS PHP ecosystem, providing common utilities used by both the client helper bundle and the core bundle. A foundational dependency for building and extending elasticMS applications.
elasticms/common-bundle provides the shared foundation code used by the elasticMS client helper bundle and the core bundle. It centralizes common services and utilities so both bundles stay consistent, avoid duplication, and remain interoperable across the elasticMS ecosystem.
Key features:
- Shared service and utility classes reused by client and core bundles
- Consistent configuration and dependency wiring across elasticMS components
- Maintained within the elasticMS mono repository
- Documented via the official elasticMS developer docs
- Simplifies upgrades by keeping common logic in one place
Frequently asked questions about Common Bundle
- Is elasticms/common-bundle compatible with Laravel?
- Not natively. It is a Symfony-oriented shared library for elasticMS, so Laravel apps need adapters for the container, event dispatcher, and HTTP layer. You can install it with Composer, but expect integration work rather than a drop-in Laravel package.
- How do I install elasticms/common-bundle in a Laravel project?
- Install it with Composer, for example composer require elasticms/common-bundle:~6.9.40 if you are stabilizing on the 6.9 line. Run composer why-not elasticms/common-bundle 6.9.40 first to catch Symfony or PHP constraint conflicts. There is no Laravel service provider, so registration and wiring are manual.
- Which Laravel, PHP, and Symfony versions does elasticms/common-bundle support?
- The package is built on Symfony components and is not versioned against Laravel, so Laravel compatibility depends on your PHP and Symfony bridge constraints. The 6.9 line is still patched at 6.9.40, while 7.x ships in parallel as a separate codebase. Check Composer metadata and test with your exact Laravel and PHP versions rather than assuming Laravel support.
- What features does elasticms/common-bundle provide?
- It contains shared utilities and services used by the elasticMS client helper and core bundles, including validation, logging, DTOs, and event-driven workflow code. It is a common layer for the elasticMS ecosystem, not a general Laravel CMS package. Confirm that its Content, Media, and multi-tenancy helpers map to your application before adopting it.
- Why would a Laravel developer use elasticms/common-bundle instead of Laravel-native packages?
- Usually only when integrating with an existing elasticMS or Symfony ecosystem and you want to reuse the same shared utilities instead of duplicating them. For a greenfield Laravel app, Laravel-native packages are simpler because this bundle lacks Eloquent and Blade abstractions. The benefit is consistency across elasticMS bundles; the cost is adapter code and ecosystem coupling.
- How do I configure elasticms/common-bundle services and events in Laravel?
- You need to bridge the Symfony container, event dispatcher, and HTTP integration into Laravel manually or through a small adapter layer. Keep configuration keys and event names under version control and diff them between releases, because patch releases can change behavior without detailed notes. Test event ordering and validation defaults after every upgrade.
- How should I test elasticms/common-bundle in a Laravel application?
- Use a sandbox branch or proof of concept with your real Laravel version, then run a full regression suite plus config and event-name diffs. Pay special attention to log levels, validation defaults, and event ordering, since the 6.9.38 to 6.9.40 patch notes are opaque. Add contract tests around any adapter you write for container, events, or HTTP.
- Is elasticms/common-bundle actively maintained and production-ready?
- The 6.9 branch is still receiving patches, with 6.9.40 being a recent patch release, and 7.x is shipping in parallel. That means 6.9 is a live supported line today, but you should confirm its EOL date and security-patch policy before relying on it long term. Community visibility is low, so budget for self-support and regression testing, and review the LGPL-3.0 obligations for your distribution model.
- What are the alternatives to elasticms/common-bundle for Laravel?
- For Laravel-only projects, prefer Laravel-native packages or direct Symfony components that already fit illuminate/support and Laravel's container. If you need elasticMS functionality, evaluate the elasticMS core and client helper bundles instead of pulling in the common layer alone. Staying on 6.9.x versus moving to 7.x is a dual-track decision, not an automatic upgrade.
- How do I plan an upgrade from elasticms/common-bundle 6.9.x to 7.x?
- Treat it as a two-step path: first move from your current 6.9 pin to 6.9.40, validate with a full regression run, then plan a bounded 6.9.40 to 7.3.x migration. The 6.9 to 7.x jump is a major-version change with sparse release notes, so expect manual changelog and code diffing plus a proof of concept. Confirm the 6.9 support window before scheduling the 7.x work.
Weaver
How can I help you explore Laravel packages today?