spatie/laravel-varnish

Laravel 9 support

leafling opened this issue · 1 comments

When I try to install laravel-varnish on Laravel 9, I get this:

% composer require spatie/laravel-varnish
Using version ^2.8 for spatie/laravel-varnish
./composer.json has been updated
Running composer update spatie/laravel-varnish
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - spatie/laravel-varnish 2.8.0 requires illuminate/console ~5.8.0|^6.0|^7.0 -> found illuminate/console[v5.8.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev] but these were not loaded, likely because it conflicts with another require.
    - spatie/laravel-varnish 2.8.1 requires illuminate/console ~5.8.0|^6.0|^7.0|^8.0 -> found illuminate/console[v5.8.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
    - spatie/laravel-varnish 2.8.2 requires illuminate/console ^6.0|^7.0|^8.0 -> found illuminate/console[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
    - spatie/laravel-varnish 2.8.3 requires illuminate/console ^8.73 -> found illuminate/console[v8.73.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires spatie/laravel-varnish ^2.8 -> satisfiable by spatie/laravel-varnish[2.8.0, 2.8.1, 2.8.2, 2.8.3].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require spatie/laravel-varnish:*" to figure out if any version is installable, or "composer require spatie/laravel-varnish:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

I initially got this error when I was trying to update an existing laravel site and then after not being able to resolve it there, I tried installing it on a fresh barebones install of Laravel 9 and got the same errors.

This is fixed in the latest release.