In short
To use a local TYPO3 extension in Composer mode, keep it in a folder of your project, add a path repository to composer.json and require it with @dev. This guide shows each step and how to deploy the extension safely.
Updated 8 November 2026 | T3Planet editorial team
Are you developing local custom TYPO3 extension development in "composer mode"? It means, your extension is not at composer server like packagist.org. No problem, Just perform below steps to install your custom local TYPO3 extension at TYPO3 composer.
Step 1: Create /extensions at root folder and put your extension
Step 2: Configure composer.json
// composer.json
"repositories": [
{
"type": "path",
"url": "extensions/*",
"options": {
"symlink": true
}
}
], Step 3: Install Extension with @dev
composer require yourvendor/yourextension:@dev Step 4: Done! Activate from Extensions Manager.
Step 5: Add classes
A class in Classes/Controller/ItemController.php uses the namespace Vendor\MyExt\Controller. After adding new class folders, run:
composer dump-autoload Deploy
Local development and deployment work differently, so keep them apart.
What belongs in the repository: composer.json, composer.lock, packages/ (your extension sources) and config/. Do not commit vendor/.
Local development: the path repository creates a symlink, so vendor/vendor/my-ext points to packages/my_ext. Edits apply at once.
Deployment: build on a clean checkout or in your CI:
git clone <your-repo> build && cd build
composer install --no-dev --optimize-autoloader
vendor/bin/typo3 extension:setup composer install reads composer.lock, so the server gets the exact versions you tested. Never run composer update on the server.
Symlinks on the server: a symlink only works if packages/ is deployed next to vendor/. If you ship only vendor/, the link breaks. Either deploy both folders or force a copy during the build:
COMPOSER_MIRROR_PATH_REPOS=1 composer install --no-dev --optimize-autoloader Check: after the build, open the TYPO3 backend (or run vendor/bin/typo3 extension:list) and confirm your extension is loaded.
Common problems
- Package not found: check that
urlmatches the folder and thatnameis valid (lowercase, with a slash). - Class not found: check the PSR-4 namespace and run
composer dump-autoload. - Extension not listed in the backend: the
typemust betypo3-cms-extensionand theextension-keymust be set. - Changes not visible: flush the caches.
Looking for ready-made extensions instead? Browse the TYPO3 Extensions.
FAQs
Add a path repository to composer.json and require the extension with @dev, as shown in the steps of this guide.
In a folder in your project that the path repository URL points to. Step 1 and the Deploy section show the layout.
No. A path repository lets Composer use an extension that exists only in your project.
Build on a clean checkout with composer install --no-dev --optimize-autoloader, run extension:setup, and deploy packages/ next to vendor/ or force a copy with COMPOSER_MIRROR_PATH_REPOS=1.
Check the PSR-4 namespace in composer.json and run composer dump-autoload.
Sanjay Chauhan
Sanjay Chauhan A young technology enthusiast and entrepreneur. At 24, he co-founded NITSAN – a TYPO3 Agency in Bhavnagar, India. I love TYPO3, I would like to furnish TYPO3 people with informative content, tutorials, and experiences by composing regular TYPO3 blogs “as to give back to the community”. Today Sanjay is CTO and a TYPO3 innovator at NITSAN.
More From Author