[Bug]: coolsam/modules ^5.0.9 conflicts with filament/filament ^5.0.0 #162
Description
What happened?
When running composer update, dependency resolution fails because coolsam/modules v5.0.9 requires filament/filament ^4.0, while my project requires filament/filament ^5.0.0. Composer reports a version conflict and refuses to install/update dependencies, so the package cannot be used in a Filament v5 project.
raw text:
➜ composer update
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires coolsam/modules ^5.0.9 -> satisfiable by coolsam/modules[v5.0.9].
- coolsam/modules v5.0.9 requires filament/filament ^4.0 -> found filament/filament[v4.0.0, ..., v4.5.3] but it conflicts with your root composer.json require (^5.0.0).
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
How to reproduce the bug
I expected coolsam/modules to be compatible with Filament v5 (or at least to have a release/branch supporting Filament v5), especially since Filament v5 does not appear to introduce major breaking changes for this kind of integration. If the incompatibility is intended due to Livewire/Filament internals, I expected documentation or constraints explaining that.
How to reproduce the bug?
Create a Laravel project and require the following packages:
"coolsam/modules": "^5.0.9",
"filament/filament": "^5.0.0",
"nwidart/laravel-modules": "^12.0.4",
"laravel/framework": "^12.47",
Package Version
^5.0.9
PHP Version
8.5.1
Laravel Version
^12.47
Which operating systems does with happen with?
Linux
Notes
This looks like a composer constraint issue rather than runtime behavior. Is there a planned release that supports filament/filament ^5.0?