Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

laravel new prints a Deprecated return-type warning from Symfony Process

ErrorDeprecated: Return type of Symfony\Component\Process\Process::getIterator(int $flags = 0)

Short answer

This warning means the global Laravel installer is running an old copy of symfony/process on a newer PHP. PHP 8.1 and later warn when a class overrides an internal method without a matching return type. Update the installer and its dependencies with Composer, or reinstall it with the official script.

  • Applies to Laravel installer, Composer 2, PHP 8.3
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    See which versions of the installer and of symfony/process sit in Composer's global directory.

    composer global show laravel/installer symfony/process
    php -v
  2. 2Match what you see, then jump to its fix

    1. 1The warning path points into ~/.composer/vendor/symfony/process (or ~/.config/composer/vendor/...)The global installer carries an old symfony/processFix
    2. 2composer global show laravel/installer lists an old versionThe installer was installed a long time ago and never updatedFix

What does the error look like?

  • Deprecated: Return type of Symfony\Component\Process\Process::getIterator(int $flags = 0)
  • laravel new still creates the project, but prints the notice above first

Cause 1 of 2

The global installer carries an old symfony/process

1Check

PHP 8.1 and later emit a deprecation notice when a class overrides an internal method such as getIterator() without a compatible return type. An old copy of symfony/process in the global directory does exactly that.

composer global show symfony/process

2Fix

Update the installer together with its dependencies, so Composer can move symfony/process to a release that works on your PHP.

composer global update laravel/installer --with-dependencies

3Verify

Run laravel new again; the notice no longer prints.

laravel new example-app

Confirmed by php.net

Did this fix it?

Cause 2 of 2

The installer was installed a long time ago and never updated

1Check

The Laravel docs install the installer with composer global require. A global package stays at the version it was installed at until you update it.

composer global outdated

2Fix

Update it with the global command, or reinstall PHP, Composer and the installer through php.new, which the docs say can be re-run to update them.

composer global update laravel/installer

3Verify

The installer prints its new version.

laravel --version

Confirmed by laravel.com

Did this fix it?

How do I stop it coming back?

  • Run composer global update every few weeks, or re-run php.new, so global tools follow PHP.
  • After every PHP upgrade, update the global Composer packages.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

composer require maatwebsite/excel fails to install

Composer says the package needs an older PHP than the one installed

Composer refuses maatwebsite/excel when the PHP version or a PHP extension does not match what the package and PhpSpreadsheet need.

3 causes, each with a fix

Back end

composer require laravel/horizon fails: ext-pcntl is missing

laravel/horizon v1.1.0 requires ext-pcntl * -> the requested PHP extension pcntl is missing from your system

Horizon needs the pcntl extension, and Composer refuses to install it where PHP lacks that extension.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.