Weave Code
Model Updater Laravel Package
laimoon/model-updater
laimoon/model-updater is a Laravel package that provides a clean, reusable way to update Eloquent models. It helps reduce boilerplate by centralizing model update logic, keeping controllers and services tidy while preserving consistent persistence behavior.
Laimoon Model Updater is a lightweight Laravel package that streamlines updating Eloquent models from request data. It offers a fluent, declarative API to assign validated attributes, sync related records, and persist changes while honoring model events and mass-assignment rules.
- Fluent updates: chain clean, readable
update()calls. - Request-friendly: map validated input directly to model attributes.
- Relationship sync: update has-many/belongs-to relations in one call.
- Event-aware: fires standard Eloquent events and observers.
- Safe assignment: respects
$fillable/$guardedand attribute casts.
Frequently asked questions about Model Updater
- What does laimoon/model-updater actually do for Laravel models?
- It is intended to provide an elegant, consistent way to update Eloquent models from request data, reducing boilerplate around applying validated input. At its core it adds an abstraction over Eloquent's fill, save, and update behavior rather than replacing the ORM. The repository description is thin, so verify the exact API and behavior in a spike before adopting it.
- Is laimoon/model-updater compatible with Laravel 10 or 11?
- Almost certainly not out of the box. The last release was in January 2020, which points to Laravel 5.5–6.x and PHP 7.x, so Composer constraints and deprecated PHP constructs are likely to block modern Laravel 10/11 and PHP 8.1+ installs. Treat compatibility as unproven until you resolve it on your actual PHP and Laravel matrix.
- How do I install laimoon/model-updater with Composer?
- The mechanical install is composer require laimoon/model-updater, with Laravel package auto-discovery handling the service provider if one is registered. Publishing config, if any, would follow the package README. The real blocker is dependency resolution on modern Laravel and PHP versions, not the install command itself.
- Is laimoon/model-updater safe to use in production?
- It carries an abandoned-package risk profile: the repository is archived, has no recent releases, roughly 40 stars, and zero dependents. That means no security patching, no PHP or Laravel compatibility maintenance, and no community support. It may be acceptable in a frozen legacy app, but for a maintained production stack, vendor it or replace it.
- Does laimoon/model-updater bypass Eloquent events or mass-assignment protection?
- The available documentation does not answer this clearly, so do not assume. Because the package layers over Model::fill(), save(), and update(), it could alter when updating and saved events fire or how guarded and fillable attributes are treated. Write a spike that asserts event dispatch and mass-assignment behavior before relying on it for audited data changes.
- Can I use laimoon/model-updater with Laravel Form Requests?
- The package is aimed at updating models from request data, so pairing it with a Form Request and passing only validated input is the sensible pattern. That keeps validation and authorization in Laravel's native layer while the package handles assignment. Confirm the exact method signature in the package source, since the README excerpt is not provided.
- Which Laravel and PHP versions does laimoon/model-updater support?
- Based on its 2020 release date, expect Laravel 5.5–6.x and PHP 7.x-era support rather than Laravel 9, 10, or 11. The package's Composer constraints are the authoritative answer, but its age makes modern support unlikely. Run a dependency resolve or composer why-not on your target branch to confirm.
- Should I replace laimoon/model-updater with native Eloquent or a trait?
- For a package this small and this old, replacement is usually cheaper than adoption. Native fill()->save(), update(), Form Requests, and observers cover most update workflows, and a single internal trait can capture any remaining convention. That removes an unmaintained dependency and keeps behavior under your team's control.
- How should I test model updates if I adopt laimoon/model-updater?
- Build a contract test around the behavior you depend on: which attributes are assigned, whether validation is expected, which Eloquent events fire, and how transactions behave. Run it against your actual Laravel and PHP versions, plus a static analysis pass such as PHPStan or Psalm. That test should fail loudly on a future framework upgrade.
- What are the alternatives to laimoon/model-updater?
- The main alternatives are native Eloquent methods, Form Requests for validation, model observers for side effects, and a small first-party trait or base model method for your update convention. If you need a maintained package, look for one with recent releases and Laravel 10/11 support rather than an archived 2020 repository. For most Laravel apps, native Eloquent plus a thin internal abstraction is enough.
Weaver
How can I help you explore Laravel packages today?