Issue Epic Closed

#96871Going to composer-only mode

Benni Mack 02/14/22, 07:45 updated 06/12/26, 02:19

Description

This issue works as an umbrella to list all things to consider (soft factors and hard requirements) if TYPO3 Core should only support Composer-based installations.

From a hard-requirement perspective

1. Migration from non-composer based installations to composer-mode installations.

> What about PackageStates.php?
> What about ext_emconf.php?
> What about modified extensions?
> How to differentiate between “TER” extensions (= updateable) and “local” / “per-project” extensions?
> What about extensions with wrong “dependencies”

2. Web-Installer setting up TYPO3 in Composer Mode
> We don’t want to loose the functionality to install TYPO3 via a Web GUI.

3. Web-Management Interface to install / remove extensions
> Somehow we want to have editors still using the Extension Manager (or whatever we want to name this) where people can search for extensions and install them.

On top:
  • Have a best practice set up for newcomers on how to work with local extensions (path repositories)
  • Make the GUI more intuitive than it is now (composer output on CLI might be tricky already)
  • What if a production system does not ship their composer.json/composer.lock during deployment?
  • What about the current “Auto-Update” feature in the Install Tool?

Reviews 0

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

History 1

  1. Christian Kuhn commented and changed status New Closed <span data-processor="relativetime" data-value="2026-06-12T02:19:02+00:00" > 06/12/26, 02:19 </span>

    Hey. I’ll close here for now: This never took off, and if we decide to drop classic mode, we’d probably start fresh and maybe link this epic.