Laravel Valet deprecations when using PHP 8.1

[alexis-riot]

Hello,

After an upgrade of PHP from 8.0.13 to 8.1, I got a lot of deprecations when using valet command.

I've run the following commands:

• composer global update
• valet install
• valet use [email protected]

There is an examples of deprecations that I have:

[...]

Deprecated: Return type of Illuminate\Container\Container::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /Users/alexisriot/.composer/vendor/illuminate/container/Container.php on line 1182

Deprecated: Return type of Illuminate\Container\Container::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /Users/alexisriot/.composer/vendor/illuminate/container/Container.php on line 1195

[...]

Deprecated: Method ReflectionParameter::getClass() is deprecated in /Users/alexisriot/.composer/vendor/illuminate/container/Container.php on line 862

Laravel Valet 2.17.1

Thanks for support.

[mattstauffer]

@alexis-riot If you upgrade to the latest version of Valet, you should be be no longer getting any of these deprecations.

[alexis-riot]

https://packagist.org/packages/laravel/valet - latest version look like 2.18.1
I have upgrade, and still have these deprecated warnings.

[...]

Deprecated: Method ReflectionParameter::getClass() is deprecated in /Users/alexisriot/.composer/vendor/illuminate/container/Container.php on line 788

Deprecated: Method ReflectionParameter::getClass() is deprecated in /Users/alexisriot/.composer/vendor/illuminate/container/Container.php on line 862

Deprecated: Method ReflectionParameter::getClass() is deprecated in /Users/alexisriot/.composer/vendor/illuminate/container/Container.php on line 788

Deprecated: Method ReflectionParameter::getClass() is deprecated in /Users/alexisriot/.composer/vendor/illuminate/container/Container.php on line 862
Laravel Valet 2.18.1

Usage:
  command [options] [arguments]

[mattstauffer]

@alexis-riot You will need to do a full composer global update, not just composer global update laravel/valet; that's a dependency that Valet allows you to have at the lower version you have right now, but if you update it, Valet will keep working but it will stop throwing those errors.

[alexis-riot]

➜  ~ composer global update
Changed current directory to /Users/alexisriot/.composer
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove
Generating autoload files
17 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

➜  ~ cat ~/.composer/composer.json
{
    "require": {
        "laravel/installer": "^4.2",
        "laravel/valet": "^2.17"
    }
}

It's what I do.

[driesvints]

I also get these now. @bram-pkg managed to solve these on his own. Hopefully he can share how he did that. I suspect through explicitly requiring the Illuminate/container dependency?

[bram-pkg]

I completely uninstalled all my global composer packages and only installed Valet at first. That decided to finally install the ^8.0 version of illuminate/container.

Before it was on ^6.0, I think. After that I installed the Forge CLI again, and it all stayed okay.

[dpslwk]

Im seeing the same warnings

~/.composer/composer.json

{
    "require": {
        "friendsofphp/php-cs-fixer": "^3.2",
        "squizlabs/php_codesniffer": "*",
        "phpstan/phpstan": "^1.3",
        "profburial/wkhtmltopdf-binaries-osx": "^0.12.1",
        "laravel/valet": "^2.18",
        "laravel/installer": "^4.2"
    }
}

its resolved illuminate/container to v5.4.36

trying to composer global require illuminate/container -W

Changed current directory to /Users/matt/.composer
Using version ^8.78 for illuminate/container
./composer.json has been updated
Running composer update illuminate/container --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
    - Conclusion: don't install illuminate/container v8.78.1 (conflict analysis result)
    - symfony/console v5.4.2 requires symfony/service-contracts ^1.1|^2|^3 -> satisfiable by symfony/service-contracts[v3.0.0].
    - laravel/installer v4.2.9 requires symfony/console ^4.0|^5.0 -> satisfiable by symfony/console[v5.4.2].
    - Root composer.json requires illuminate/container ^8.78 -> satisfiable by illuminate/container[v8.78.0, v8.78.1].
    - Conclusion: don't install psr/container[1.1.2] | install psr/container[2.0.2] (conflict analysis result)
    - Conclusion: don't install psr/container 2.0.2 (conflict analysis result)
    - laravel/installer is locked to version v4.2.9 and an update of this package was not requested.
    - illuminate/container v8.78.0 requires psr/container ^1.0 -> satisfiable by psr/container[1.0.0, 1.1.0, 1.1.1, 1.1.2].
    - You can only install one version of a package, so only one of these can be installed: psr/container[1.0.0, 1.1.0, 1.1.1, 1.1.2, 2.0.0, 2.0.1, 2.0.2].
    - symfony/service-contracts v3.0.0 requires psr/container ^2.0 -> satisfiable by psr/container[2.0.0, 2.0.1, 2.0.2].
    - Conclusion: don't install psr/container 2.0.1 (conflict analysis result)

removed laravel/install
composer remove laravel/installer
and ran into conflicts with friendsofphp/php-cs-fixer

composer global require illuminate/container -W

Changed current directory to /Users/matt/.composer
Using version ^8.78 for illuminate/container
./composer.json has been updated
Running composer update illuminate/container --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
  Problem 1
    - Conclusion: don't install illuminate/container v8.78.1 (conflict analysis result)
    - symfony/stopwatch v6.0.0 requires symfony/service-contracts ^1|^2|^3 -> satisfiable by symfony/service-contracts[v3.0.0].
    - friendsofphp/php-cs-fixer v3.4.0 requires symfony/stopwatch ^4.4.20 || ^5.0 || ^6.0 -> satisfiable by symfony/stopwatch[v6.0.0].
    - Root composer.json requires illuminate/container ^8.78 -> satisfiable by illuminate/container[v8.78.0, v8.78.1].
    - Conclusion: don't install psr/container[1.1.2] | install psr/container[2.0.2] (conflict analysis result)
    - Conclusion: don't install psr/container 2.0.2 (conflict analysis result)
    - friendsofphp/php-cs-fixer is locked to version v3.4.0 and an update of this package was not requested.
    - illuminate/container v8.78.0 requires psr/container ^1.0 -> satisfiable by psr/container[1.0.0, 1.1.0, 1.1.1, 1.1.2].
    - You can only install one version of a package, so only one of these can be installed: psr/container[1.0.0, 1.1.0, 1.1.1, 1.1.2, 2.0.0, 2.0.1, 2.0.2].
    - symfony/service-contracts v3.0.0 requires psr/container ^2.0 -> satisfiable by psr/container[2.0.0, 2.0.1, 2.0.2].
    - Conclusion: don't install psr/container 2.0.1 (conflict analysis result)

[dpslwk]

I just did composer selfupdate and then composer global update finally moved up the illuminate packages to v8

$ composer selfupdate                                                   
Upgrading to version 2.2.4 (stable channel).
   
Use composer self-update --rollback to return to version 2.1.9

$ composer update                                                       
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 4 updates, 0 removals
  - Upgrading illuminate/container (v5.4.36 => v8.78.1)
  - Upgrading illuminate/contracts (v5.4.36 => v8.78.1)
  - Downgrading psr/container (2.0.2 => 1.1.2)
  - Locking psr/simple-cache (1.0.1)
  - Downgrading symfony/service-contracts (v3.0.0 => v2.4.1)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 4 updates, 0 removals
  - Downloading illuminate/contracts (v8.78.1)
  - Downgrading psr/container (2.0.2 => 1.1.2): Extracting archive                                           
  - Downgrading symfony/service-contracts (v3.0.0 => v2.4.1): Extracting archive
  - Installing psr/simple-cache (1.0.1): Extracting archive
  - Upgrading illuminate/contracts (v5.4.36 => v8.78.1): Extracting archive
  - Upgrading illuminate/container (v5.4.36 => v8.78.1): Extracting archive
Generating autoload files                                                                                    
30 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

[driesvints]

In the meantime I've figured out this is because Laravel v8 doesn't allows psr/container 2.0 so we'll have to wait until Laravel v9 before these will go away.

[jpmaga]

Hello everyone. I was getting these deprecated warnings as well. Managed to solve it by adding a version constraint for php in composer.json, like so:

(I only have projects using either 7.4 or 8.1 at the moment.)

{
    "php": "^7.4|^8.1",
    "require": {
        "laravel/valet": "^2.17",
        "laravel/installer": "^4.1"
    }
}

and then just rm -fr ~/.composer/vendor && composer global update. Hope this also works for you.

[driesvints]

Hey all, #1181 was merged so hopefully these errors are now resolved. I'm not getting them anymore.