Issue Bug Accepted Orphaned

#109666Composer class loader errors during upgrade from v13.4.28 to v14.3.0

Benjamin Franzke 04/21/26, 10:28 updated 05/07/26, 10:08

Description

composer update

 [snip]

  - Upgrading typo3/cms-info (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-install (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-lowlevel (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-reports (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-rte-ckeditor (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-tstemplate (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-viewpage (v13.4.28 => v14.3.0): Extracting archive
Generating autoload files

In ClassAliasMapGenerator.php line 139:

  [Error]                                                                  
  Class "TYPO3\ClassAliasLoader\IncludeFile\CaseSensitiveToken" not found  

Exception trace:
  at […]/vendor/typo3/class-alias-loader/src/ClassAliasMapGenerator.php:139
 TYPO3\ClassAliasLoader\ClassAliasMapGenerator->generateAliasMapFiles() at /usr/share/composer

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Composer class loader errors during upgrade from v13.4.28 to v14.3.0 Resolves: #109666 Releases: main

History 6

  1. Helmut Hummel commented <span data-processor="relativetime" data-value="2026-04-21T10:39:23+00:00" > 04/21/26, 10:39 </span>

    maybe recommend using

    composer update --no-plugins && composer install

    ?

  2. Helmut Hummel commented <span data-processor="relativetime" data-value="2026-05-07T10:04:04+00:00" > 05/07/26, 10:04 </span>

    It is really hard to not break composer plugins when wanting to do significant code change on them (major upgrade).
    I also don’t think this here can be fixed easily.
    When the old plugin is installed, the code will run
    and produce a non working setup, as the runtime expects a different layout.
    Best thing we could do is to suppress the install error. But then runtime still is broken until a new composer du is performed.

    With quite some time investment, it might be possible to keep old build time and old runtime code around, partially defeating
    the intent of shipping a clean new major version.

    If this is considered important enough though, I’m happy to review pull requests here https://github.com/TYPO3/class-alias-loader/

    Benjamin Franzke wrote in #note-3:

    > I guess our users would prefer fixing this instead, also see:
    > https://typo3.slack.com/archives/C025BQLFA/p1776768317917299
    > https://typo3.slack.com/archives/C025BQLFA/p1776769959527129?thread_ts=1776768317.917299&cid=C025BQLFA

    From the single thread referenced here I can’t see any preference stated from users, but confirmation of what is broken.
    I don’t necessarily read from that, that composer update --no-plugins && composer install ins’t an acceptable fix.