Development mode response times have increased 10x after migration. about laminas-zendframework-bridge HOT 4 CLOSED

One trick you can use is to audit your third-party libraries for usage of Zend Framework and/or legacy Apigility packages; the easiest way to determine that is running composer show and seeing if any were installed. If none are being used, you can add the following to your composer.json file:

"provide": {
    "laminas/laminas-zendframework-bridge": "*"
}

(And remove any entry in the require section, if present.)

After making your changes, run composer update.

Essentially, the autoloading that the bridge package provides is unnecessary if there are no ZF packages installed. If you've run the migration tooling, your configuration should have been rewritten, and there's no more need for the bridge. The above essentially prevents installation of the package, fixing the issues you're seeing.

from laminas-zendframework-bridge.

@weierophinney
Should we add this hint to the migration guide?

from laminas-zendframework-bridge.

Should we add this hint to the migration guide?

Yes. To be honest, I thought we already had 😦 .

from laminas-zendframework-bridge.

Thanks @weierophinney. I had to use replace instead of provide in composer.json but response times are as expected now. replace will also remove the module from modules.config.php. As far as I am concerned this can be closed because there is a workaround.

from laminas-zendframework-bridge.