Weave Code
Bones Marshal Laravel Package
genealabs/bones-marshal
A Laravel/PHP package from GeneaLabs, part of the Bones ecosystem. Bones Marshal provides marshalling-style coordination utilities for Bones-based applications, aimed at developers building Laravel projects with GeneaLabs components.
Commanding and Eventing package.
Frequently asked questions about Bones Marshal
- What is genealabs/bones-marshal used for?
- Bones Marshal is a Laravel/PHP package from GeneaLabs that provides marshalling-style coordination utilities for commanding and eventing in Bones-based applications. It is intended for projects already using GeneaLabs Bones components rather than as a general-purpose Laravel command bus or event dispatcher. Check the repository README for the exact APIs and supported workflows.
- How do I install genealabs/bones-marshal with Composer?
- Install it with Composer using composer require genealabs/bones-marshal. Because it belongs to the Bones ecosystem, review its Composer dependencies to confirm any related GeneaLabs packages are installed and compatible. After installation, check the README for service provider registration or publishable configuration steps.
- Does bones-marshal support Laravel 10 or Laravel 11?
- Laravel version support is defined by the package's composer.json constraints, so check those before installing in Laravel 10, 11, or newer projects. The repository and Packagist metadata are the authoritative source for supported PHP and Laravel versions. If your app uses other Bones packages, confirm their constraints match as well.
- Is bones-marshal a standalone package or does it require other Bones packages?
- It is part of the GeneaLabs Bones ecosystem, so it is not primarily designed as a standalone utility for arbitrary Laravel apps. You will likely need other Bones components or conventions in place for commanding and eventing to work as intended. Review the package dependencies and README before adding it to a non-Bones project.
- How do commanding and eventing work in Bones Marshal?
- Bones Marshal is described as a commanding and eventing package, providing marshalling-style coordination utilities for Bones-based applications. The exact command and event APIs, dispatch patterns, and listeners should be taken from the repository README and source code. Do not assume Laravel-native command bus behavior without verifying the package docs.
- How do I configure Bones Marshal in a Laravel app?
- Configuration details depend on the package version and how it integrates with your Bones application. Start by checking the README for service provider auto-discovery, config publishing, and any required environment variables. In Laravel, verify package discovery and clear config caches after installation.
- Can I use Bones Marshal in production?
- You can evaluate Bones Marshal for production by checking its release history, test coverage, dependency constraints, and open issues in the GeneaLabs repository. Because it is part of the Bones ecosystem, production readiness also depends on the stability of your other Bones components. Pin a tested version in composer.json and run your application's test suite before deploying.
- How do I test an app that uses Bones Marshal?
- Test apps using Bones Marshal with your normal Laravel testing setup, including feature tests that dispatch commands or events and assert the resulting behavior. If the package exposes fakes or testing helpers, use them as documented in the README. Otherwise, isolate integration points and mock external Bones services where practical.
- What are alternatives to genealabs/bones-marshal?
- Alternatives depend on what you need: Laravel's built-in command bus, events and listeners, or other Laravel event-sourcing and command packages may fit non-Bones projects. If you are already using GeneaLabs Bones components, staying with Bones Marshal is likely the most consistent choice. Compare APIs, maintenance activity, and dependency fit before switching.
- Is genealabs/bones-marshal actively maintained?
- Check the GitHub repository for recent commits, releases, and issue activity to judge maintenance status. Also review Packagist release dates and version constraints for compatibility with current Laravel versions. If activity is low, pin a known-good version and be prepared to maintain a fork if necessary.
Weaver
How can I help you explore Laravel packages today?