The TYPO3 Extension Repository (TER) has traditionally been the primary location for sharing and discovering extensions for TYPO3 CMS. However, with the evolution of TYPO3 and the adoption of Composer, a fragmented landscape emerged where extensions could be found both in TER and on Packagist, the main Composer repository. This duality made it challenging for users to discover all available extensions in a centralized manner. Recognizing this challenge, a new integration has been implemented to bridge the gap between TER and Packagist, ensuring that extensions published on Packagist are also visible in TER.
The integration between TYPO3 TER and Packagist is designed to automatically import extensions from Packagist that are marked with the specific type typo3-cms-extension into the TYPO3 Extension Repository. This process enables a centralized view of available extensions, facilitating easier discovery and access for users.
For an extension to be automatically imported from Packagist to TER, it must meet the following criteria in the composer.json file:
There are specific conditions under which a Composer package will not be imported into TER:
An imported Composer package will be automatically removed from the TYPO3 Extension Repository (TER) under the following circumstances:
Extensions that are available exclusively on Packagist and imported into TER will be identifiable by a standard icon (a package) to distinguish them from those directly uploaded to TER. While download statistics for these extensions are not initially available, there are plans to incorporate this feature in the future.