Version issues, can not install

[mgkimsal]

Completely fresh laravel 10.x install using php 8.2

$ laravel new demo2
$ cd demo2
$ composer require cheesegrits/filament-google-maps

Using version ^3.0 for cheesegrits/filament-google-maps
./composer.json has been updated
Running composer update cheesegrits/filament-google-maps
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - cheesegrits/filament-google-maps[v3.0.0, ..., v3.0.9] require geocoder-php/google-maps-provider ^4.7 -> satisfiable by geocoder-php/google-maps-provider[4.7.0, 4.7.1].
    - geocoder-php/google-maps-provider[4.7.0, ..., 4.7.1] require geocoder-php/common-http ^4.0 -> satisfiable by geocoder-php/common-http[4.0.0, ..., 4.5.0].
    - geocoder-php/common-http[4.0.0, ..., 4.2.0] require php ^7.0 -> your php version (8.2.9) does not satisfy that requirement.
    - geocoder-php/common-http 4.3.0 requires php ^7.2 -> your php version (8.2.9) does not satisfy that requirement.
    - geocoder-php/common-http[4.4.0, ..., 4.5.0] require psr/http-message ^1.0 -> found psr/http-message[1.0, 1.0.1, 1.1] but the package is fixed to 2.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 cheesegrits/filament-google-maps ^3.0 -> satisfiable by cheesegrits/filament-google-maps[v3.0.0, ..., v3.0.9].

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 cheesegrits/filament-google-maps:*" to figure out if any version is installable, or "composer require cheesegrits/filament-google-maps:^2.1" if you know which you need.

Note:

$ composer require cheesegrits/filament-google-maps  -W

seems to work, but forcing with the -W never feels correct.

[digitall-it]

Issue #52 is a possible duplicate of this.

[kevindesousa]

Hi, no news ?

[digitall-it]

@kevindesousa this seems it will take a bit, meanwhile everything works ok with forced downgrade of dependencies. I personally have chosen to start using the component as it is, as soon as the dependency requirement is updated upon testing of the version, we'll receive it on the subsequent semver update, if it doesn't break or change anything.