Fix package installation error

[relliv]

After first installation command (composer global require laravel-ready/packager --dev) console prints this error

Changed current directory to /Users/eyuperdogan/.composer
./composer.json has been updated
Running composer update laravel-ready/packager
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - laravel-ready/packager[1.0.0, ..., 1.2.0] require illuminate/filesystem v8.83.18 -> satisfiable by illuminate/filesystem[v8.83.18].
    - laravel-ready/packager v1.4.0 requires illuminate/support ^v9.9.0 -> satisfiable by illuminate/support[v9.9.0, ..., v9.52.16].
    - laravel-ready/packager v1.3.0 requires illuminate/support ^8.8 || ^v9.0 -> satisfiable by illuminate/support[v8.8.0, ..., v8.83.27, v9.0.0, ..., v9.52.16].
    - illuminate/support[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.2.10) does not satisfy that requirement.
    - illuminate/support[v8.12.0, ..., v8.83.27] require illuminate/collections ^8.0 -> found illuminate/collections[v8.0.0, ..., v8.83.27] but the package is fixed to v10.21.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - illuminate/filesystem v8.83.18 require illuminate/collections ^8.0 -> found illuminate/collections[v8.0.0, ..., v8.83.27] but the package is fixed to v10.21.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - illuminate/support[v9.0.0, ..., v9.52.16] require illuminate/collections ^9.0 -> found illuminate/collections[v9.0.0, ..., v9.52.16] but the package is fixed to v10.21.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires laravel-ready/packager * -> satisfiable by laravel-ready/packager[1.0.0, 1.2.0, v1.3.0, v1.4.0].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require laravel-ready/packager:*" to figure out if any version is installable, or "composer require laravel-ready/packager:^2.1" if you know which you need.

and it's working fine with composer global require laravel-ready/packager --dev -W command but this should fix.