Error installing CLI packages - Fatal error: Allowed memory size exhausted

Support
, ,
11

I’ve never removed a package like that either, but it should be similar to removing one with composer (that’s what wpcli uses under the hood).

I forgot to ask and continue investigating this line of thought… how and where did you make this change? Did you verify that the settings were applied?

I read this FAQ within the wpcli handbook:

The above link mentions that there might be an additional php.ini file. This isn’t something that Local would put in place, but maybe if this site has been imported from another host, there would be an additional file. Here’s the general workflow I would try:

  1. Update the values for the site within ~/Local Sites/sitename/conf/php/php.ini.hbs
    • Any changes you make to this site configuration, need to include a restart of the site in Local (stop site, and then start again). This is so Local can re-compile the .hbs file into the actual running configuration for the site.
    • Try installing your package again after doing this
  2. Find additional php.ini files. Right-click on the site in Local and select “Open Site Shell”
    • Within the shell, use this find command:
    find . -name 'php.ini'
  3. Try installing the package by increasing memory at runtime. I found this in the above linked FAQ doc:
    php -d memory_limit=512M "$(which wp)" package install <package-name>
    • You might need to go quite high. Depending on how much ram you have, I’d keep increasing that limit to 1024M, 2048M or more!