Weave Code
Memento Laravel Package
assisted-mindfulness/memento
Memento is a Laravel package for capturing and restoring Eloquent model snapshots, making it easy to add undo, versioning, or audit-style history to your app. Lightweight, configurable, and simple to integrate into existing models and workflows.
Memento is a small function that stores cache only within a single request or job.
Frequently asked questions about Memento
- What is the assisted-mindfulness/memento package used for?
- Memento is a small Laravel package intended for request- or job-scoped caching; its own description says it stores cache only within a single request or job. The package blurb also describes capturing and restoring Eloquent model snapshots for undo, versioning, or audit-style history. Confirm the exact API in the repository README before designing around either use case.
- How do I install Memento in a Laravel application?
- Install it with Composer using composer require assisted-mindfulness/memento. The package follows standard Laravel package conventions and supports framework auto-discovery, so manual service provider registration should not be required. After installing, run your application test suite to confirm the integration works in your environment.
- Which Laravel and PHP versions does Memento 3.0 support?
- Version 3.0.0 is described as a support-matrix realignment release targeting Laravel 10, PHP 8.2, and PHPUnit 10. The published notes do not state whether Laravel 11 or 12 and PHP 8.3 or 8.4 are also supported. Check the composer.json constraints in the 3.0.0 tag before adopting it.
- Is upgrading Memento from 2.x to 3.0 a breaking change?
- Yes, it is a semver-major release, and the only documented change is a platform support realignment. That almost always means older Laravel or PHP versions were dropped, which is breaking for consumers even if the public API is unchanged. Review the full 2.0.0 to 3.0.0 diff because the release notes do not include an upgrade guide.
- Does Memento work with Laravel 11 or Laravel 12?
- The 3.0.0 release notes mention Laravel 10, so Laravel 11 and 12 support is not confirmed by the published information. Do not assume forward compatibility until you inspect the composer.json require constraints in the 3.0.0 tag. If your app runs Laravel 11 or 12, treat adoption as a compatibility spike rather than a routine update.
- Do I need to publish config files or run migrations for Memento?
- The available release information does not advertise any config rewrite, migration script, or codemod for the 3.0.0 upgrade. The package is described as lightweight and simple to integrate into existing models and workflows. Still, diff any published config, assets, or migrations between 2.0.0 and 3.0.0 before deploying.
- Does Memento include test helpers affected by the PHPUnit 10 upgrade?
- The 3.0.0 release moves the package to PHPUnit 10, but the notes do not say whether Memento exposes test helpers, traits, or fixtures. If it does, PHPUnit 9 to 10 removed several APIs and changed the phpunit.xml schema, so your own tooling may need changes. Confirm this by inspecting the package source and test directory.
- How does Memento differ between request-scoped cache and model snapshots?
- The package description says Memento stores cache only within a single request or job, which suggests a lightweight in-request memoization helper. The blurb separately describes capturing and restoring Eloquent model snapshots for undo, versioning, or audit history. Because these descriptions diverge, read the README and source to determine which capability your target version actually provides.
- Is Memento safe to use in production?
- It is a small Composer-installable Laravel package with low operational overhead, but the 3.0.0 release notes provide no CI matrix, test results, or regression evidence. The release appears to come from a single contributor without a documented long-term support policy. Pin exact versions, review the diff, and run your full test suite plus targeted smoke tests before production rollout.
- What should I check before upgrading to Memento 3.0.0?
- Verify the exact composer.json matrix for Laravel and PHP, review the full 2.0.0 to 3.0.0 diff, and check for transitive dependency conflicts with packages still pinning the 2.x line. Run a spike branch through your CI matrix and a non-production soak while production stays pinned to 2.x. Only then should you bump the constraint to ^3.0 deliberately.
Weaver
How can I help you explore Laravel packages today?