Weave Code
Cleaner Bundle Laravel Package
lamoda/cleaner-bundle
A lightweight Symfony bundle from Lamoda that provides reusable cleaner services for sanitizing and normalizing application data. Configure cleaning rules, integrate them into PHP workflows, and keep input and domain data consistent with minimal boilerplate.
lamoda/cleaner-bundle is a Symfony bundle that integrates the Lamoda Cleaner library into Symfony applications. It provides bundle configuration and dependency-injection wiring so cleaner services can be registered, configured, and reused consistently across a project.
- Symfony bundle integration and service registration
- Configurable cleaner services via DI
- Reusable cleaning rules and pipelines
- Extensible for custom cleaner implementations
- Lightweight setup for existing Symfony apps
Frequently asked questions about Cleaner Bundle
- What is lamoda/cleaner-bundle?
- lamoda/cleaner-bundle is a Symfony bundle that registers and configures services from the lamoda/cleaner library, which is intended for clearing old data from different storages. It is not a Laravel package; its only job is dependency-injection and configuration inside a Symfony kernel. The bundle itself contains little logic beyond service definitions and a config tree.
- Can I use lamoda/cleaner-bundle in a Laravel application?
- Not idiomatically. Laravel has no Symfony bundle registration mechanism, so the bundle class and Resources/config service definitions are inert in a Laravel app. You would need to depend on the core lamoda/cleaner library directly or reimplement the small amount of logic you need.
- How do I install lamoda/cleaner-bundle with Composer?
- You can run composer require lamoda/cleaner-bundle, but it is a Symfony bundle and will not integrate with Laravel's package discovery or service container. A 2021 Symfony bundle may also conflict with Symfony component versions used by modern Laravel. Expect Composer resolution problems before you reach runtime.
- Is lamoda/cleaner-bundle still maintained?
- No. The repository is archived, the last release was 2021-08-11, and it has roughly 2 stars and 0 dependents. There is no active maintainer, no security response path, and no guarantee of fixes. Any defect becomes your responsibility.
- Does lamoda/cleaner-bundle support PHP 8.2, 8.3, or 8.4?
- There are no compatibility guarantees. The bundle was last released in 2021, before modern PHP 8.x versions were common, and the archived repository shows no evidence of testing against them. Check the core lamoda/cleaner library's own constraints and release history if you are considering it.
- How do I clear old data from storages in Laravel without this bundle?
- For a narrow need such as ordered deletion of old records, implement a first-party Artisan command or queued job against Eloquent or your storage API. Use Laravel's scheduler to run it and test it with database transactions or a dedicated test database. Only vendor the core library if the capability is genuinely substantial and you have verified its maintenance status.
- Does lamoda/cleaner depend on Doctrine ORM or DBAL?
- That must be verified in the core library's composer.json before any adoption. If it depends on Doctrine ORM or DBAL, it is structurally misaligned with Laravel's Eloquent ecosystem and would require an adapter layer. For a small cleanup utility, that adapter cost usually outweighs the benefit.
- Is lamoda/cleaner-bundle safe to use in production?
- It is not recommended for production Laravel applications. The bundle is abandoned, has no security response path, and may pull unmaintained transitive dependencies into your lockfile. If you must use related code, isolate it to dev or test tooling and consider forking only the core library under your own organization.
- What are alternatives to lamoda/cleaner-bundle for Laravel?
- For most Laravel cleanup tasks, a first-party command or service using Eloquent, the scheduler, and database cascades is simpler and safer. Laravel's prune commands and model events can cover common cases. Treat lamoda/cleaner as reference material rather than a dependency.
- How much work is it to replace lamoda/cleaner-bundle in Laravel?
- The bundle layer is trivial to replace: its service definitions and config tree can be rewritten as a Laravel ServiceProvider with bindings and a published config file. A half-day spike to read the service definitions and the core library's public API is usually enough. Then decide whether to implement the narrow capability in first-party code or vendor the core library only after checking its maintenance and PHP 8.x compatibility.
Weaver
How can I help you explore Laravel packages today?