Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
\Drupal\Core\Composer\Composer::preAutoloadDump() contains a list of critical code that is required for all Drupal bootstraps. This was last updated for Symfony 4 and it is possible that Symfony 5/6 has added or removed things to this list.
Steps to reproduce
Proposed resolution
Analyse the classes required for bootstrap and update the list.
Figure out if there is a way of automating this or adding test coverage.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | interdiff.3293286.5-6.txt | 1.25 KB | longwave |
| #6 | 3293286-6.patch | 5.37 KB | longwave |
| #6 | 3293286-6-test-only.patch | 2.63 KB | longwave |
| #5 | 3293286-5.patch | 5.71 KB | longwave |
| #5 | 3293286-5-test-only.patch | 2.97 KB | longwave |
Comments
Comment #2
alexpott@longwave asked about testing thhis. I think we could add a module that records the loading classes in middleware which runs right after page cache and then ensures that they are in static classmap from composer. We might have to add some exceptions. Core modules are pita because we don’t get them via composer. Otherwise the db drivers could influence this in the regular composer way.
I also think we could consider adding a tool to core to use PHP’s class preloading feature to preload all the classes used up to a cached page response.
Comment #3
catchCross posting #2704571: Add an APCu classloader with a single entry - for recording early-bootstrap classes we'd probably want an caching autoloader with a killswitch so it stops lookup at an arbitrary point in the request.
Comment #4
longwaveWe only need the classmap until the container is initialised, so to do this we can replace the container with a logging container that records the classes loaded up until that point.
The whole test feels like a bit of a hack and relies on some Composer internals, but hopefully these won't change too much in the future.
Comment #5
longwaveComment #6
longwaveWe don't need to rely on Composer internals, there is a public method we can use.
Comment #11
alexpottI still think we should be adding all the classes that are used up to serving a cached page via middleware. Both Drupal and our dependencies. We should try to validate the classmap in core/composer.json too.
Comment #12
longwaveI thought sites that cared about performance would be using apcu which takes over at that point? The apcu prefix is set immediately after container init.