Weave Code
Chang Laravel Package
phpmob/chang
phpmob/chang is a lightweight Laravel/PHP package offering a simple, focused utility for application tasks. It installs via Composer and follows Laravel conventions; see the repository README for setup, configuration, and usage examples.
Symfony 4 Bundler.
Frequently asked questions about Chang
- What is phpmob/chang and what problem does it solve?
- phpmob/chang is a lightweight Laravel and PHP package for structured change handling. It gives you a small, configurable API for recording changes and applying them through handlers, so you can express audit trails, synchronization steps, or update pipelines without building bespoke plumbing. It is Composer-installed and registered through a Laravel service provider, so it follows standard package conventions.
- How do I install phpmob/chang in a Laravel application?
- Install it with Composer using composer require phpmob/chang. Laravel's package auto-discovery should register the service provider; if your app does not use discovery, add the provider to your providers list as described in the README. Then publish the configuration file and review the defaults before using the API.
- Which Laravel and PHP versions does phpmob/chang support?
- The repository README and the package's composer.json constraints are the authoritative source for supported Laravel and PHP versions. Check those constraints against your own framework matrix rather than assuming compatibility from a changelog line. If you are pinned to an older Laravel release, verify before adding the dependency to a production application.
- How do I publish and customize the phpmob/chang configuration?
- Use Laravel's vendor:publish Artisan command and select the tag or provider that belongs to phpmob/chang, as documented in the README. The published config file is where you adjust the package's behavior, including how changes are defined and which handlers are used. Commit the published config so configuration drift is visible in code review.
- How do I define and apply a change with phpmob/chang?
- The package exposes a simple, expressive API for defining a change and then applying it through the configured handler workflow. Exact method names and examples are in the repository README, so follow those snippets rather than guessing at signatures. In practice you define the change, hand it to the package, and let the configured handler perform the work.
- Can I add custom change handlers to phpmob/chang?
- Yes. The package is designed around extensible handlers so you can implement custom change workflows and wire them in through configuration. That makes it reasonable to adapt the package to audit logging, synchronization, or update pipelines specific to your domain. Keep your handlers small and test them in isolation so upgrades stay predictable.
- Why did phpmob/chang 4.1.1 remove bundled locale support?
- Version 4.1.1 moves locale handling out of the package and treats it as an external concern supplied by the host application or a separate package. This is a decomposition of the package's surface area, shifting it from batteries-included i18n toward a core capability plus opt-in extension. Confirm with the maintainers or changelog whether the replacement is a first-party package, a documented recipe, or bring-your-own.
- Is upgrading from phpmob/chang 4.1.0 to 4.1.1 a breaking change?
- Behaviorally, yes for applications that relied on bundled locale handling: code still compiles but may resolve locales differently after the patch upgrade. Removing a capability is normally a major version change under semver, so treat this as a minor-to-moderate migration despite the patch number. Pin to 4.1.0 if you are not ready to perform the manual locale install.
- How should I test phpmob/chang integration before deploying?
- Inventory locale usage first: config keys, translation helper calls, middleware, URL or session locale persistence, and published language files under your lang directory. Orphaned language files can mask the removal in testing while the runtime loader no longer reads them, so verify which loader is actually in use. Then complete the manual locale install and re-run your locale-dependent test suite before deploying.
- What are alternatives to phpmob/chang, and is it production-ready?
- Alternatives depend on your use case: Laravel's built-in events and audit packages like activity-log implementations cover many change-recording needs, and dedicated i18n packages handle locale concerns separately. phpmob/chang is small and dependency-conscious, but its patch-release locale removal suggests you should not rely on automated dependency bumps to catch behavioral changes. Review the changelog and support policy, pin versions deliberately, and validate upgrades in staging before production.
Weaver
How can I help you explore Laravel packages today?