---
title: "Deprecation: #109027 - Move language:update command and events to EXT:core"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-109027-1771514240"
source: "Changelog/14.2/Deprecation-109027-MoveLanguageUpdateCommandAndEventsToEXTcore.rst"
typo3-version: "14.2"
typo3-major: 14
type: "deprecation"
issue: 109027
forge: "https://forge.typo3.org/issues/109027"
tags: ["CLI", "PHP-API", "FullyScanned", "ext:install"]
rendered: "2026-09-25T23:17:45+00:00"
---

# Deprecation: #109027 - Move `language:update` command and events to `EXT:core` {#deprecation-109027-1771514240}

See [forge#109027](https://forge.typo3.org/issues/109027)

## Description {#description}

The `language:update` CLI command and related
`\TYPO3\CMS\Install\Service\LanguagePackService` have been moved from
`EXT:install` to `EXT:core`, allowing installations to update language packs
without `EXT:install` having to be installed.

Since TYPO3 v13 it has been possible to run TYPO3 without `EXT:install` in
Composer-based installations. However, the `language:update` command still
required `EXT:install`, which was impractical for deployments that needed to
update language packs.

The following classes have been moved, and their old class names deprecated:

-   `\TYPO3\CMS\Install\Command\LanguagePackCommand` is now
    `\TYPO3\CMS\Core\Command\UpdateLanguagePackCommand`
-   `\TYPO3\CMS\Install\Service\Event\ModifyLanguagePackRemoteBaseUrlEvent`
    is now `\TYPO3\CMS\Core\Localization\Event\ModifyLanguagePackRemoteBaseUrlEvent`
-   `\TYPO3\CMS\Install\Service\Event\ModifyLanguagePacksEvent` is now
    `\TYPO3\CMS\Core\Localization\Event\ModifyLanguagePacksEvent`

The old class names are registered as aliases via
`\TYPO3\ClassAliasLoader\ClassAliasMap` and
continue to work in TYPO3 v14. Event listeners registered for the deprecated
event class names are still called when the new event is dispatched, with a
deprecation notice triggered at runtime.

## Impact {#impact}

Using the old class names will trigger a deprecation notice. The extension
scanner will report usage of the deprecated class names.

The old class names will be removed in TYPO3 v15.

## Affected installations {#affected-installations}

Extensions that use one or more of the deprecated class names listed above.

## Migration {#migration}

Replace the old class names with the new ones in `use` statements:

**EXT:my_extension/Classes/EventListener/MyEventListener.php**

```diff
 <?php

 declare(strict_types=1);

 namespace MyVendor\MyExtension\EventListener;

 use TYPO3\CMS\Core\Attribute\AsEventListener;
-use TYPO3\CMS\Install\Service\Event\ModifyLanguagePacksEvent;
+use TYPO3\CMS\Core\Localization\Event\ModifyLanguagePacksEvent;

 final class MyEventListener
 {
     #[AsEventListener(
         identifier: 'my-extension/modify-language-packs',
     )]
     public function __invoke(
         ModifyLanguagePacksEvent $event,
     ): void {
         // ...
     }
 }
```

**EXT:my_extension/Classes/EventListener/MyOtherEventListener.php**

```diff
 <?php

 declare(strict_types=1);

 namespace MyVendor\MyExtension\EventListener;

 use TYPO3\CMS\Core\Attribute\AsEventListener;
-use TYPO3\CMS\Install\Service\Event\ModifyLanguagePackRemoteBaseUrlEvent;
+use TYPO3\CMS\Core\Localization\Event\ModifyLanguagePackRemoteBaseUrlEvent;

 final class MyOtherEventListener
 {
     #[AsEventListener(
         identifier: 'my-extension/modify-language-pack-remote-base-url',
     )]
     public function __invoke(
         ModifyLanguagePackRemoteBaseUrlEvent $event,
     ): void {
         // ...
     }
 }
```

> [!NOTE]
> Extensions supporting both TYPO3 v13 and v14 do not need to change
> anything. The old class names continue to work in both versions.
> Simply update the `use` statements when dropping TYPO3 v13 support.