PHPackages                             vever001/composer-installers-dir - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. vever001/composer-installers-dir

ActiveComposer-plugin[Utility & Helpers](/categories/utility)

vever001/composer-installers-dir
================================

Small composer plugin using composer/installers that allows you to add an additional directory to package destinations.

120PHP

Since Aug 2Pushed 6y ago1 watchersCompare

[ Source](https://github.com/vever001/composer-installers-dir)[ Packagist](https://packagist.org/packages/vever001/composer-installers-dir)[ RSS](/packages/vever001-composer-installers-dir/feed)WikiDiscussions master Synced 2mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

Composer Installers Dir
=======================

[](#composer-installers-dir)

The `composer-installers-dir` is a small composer plugin that allows you to specify a directory where all packages handled by `composer/installers` will be downloaded to.

Composer supports overriding the vendor location using `vendor-dir` out of the box.
This is not the case for packages using `composer/installers`.
This project allows you to define similarly an `installer-dir` in the `extra` section of your `composer.json`.

To install it:

```
composer require vever001/composer-installers-dir
```

This is useful if you have a composer project and you want to build it to another folder (e.g: for production release). Here's an example to build the whole project in a `dist` folder for production release:

```
DIR="dist"
composer config vendor-dir "$DIR/vendor"
composer config extra.installer-dir "$DIR"
composer install --no-dev
composer config --unset extra.installer-dir
composer config --unset vendor-dir
cp composer.json composer.lock $DIR
composer dump-autoload --working-dir="$DIR" --no-dev --optimize
```

Which will:

- Add the following in the composer.json ```
      "extra": {
        ...
        "installer-dir": "dist"
      },
      "config": {
        ...
        "vendor-dir": "dist/vendor"
      }

    ```
- Build the project to the `dist` folder (with `--no-dev`)
- Revert the changes to the `composer.json`
- Copy `composer.json` and `composer.lock` to the `dist` folder
- Update the autoloader in the `dist` folder to resolve paths

###  Health Score

19

—

LowBetter than 10% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity8

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity36

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/af6c48bc2364d3ab651d073ed09fbb61425c8af65787ad84ad683727e3b2b293?d=identicon)[vever001](/maintainers/vever001)

---

Top Contributors

[![vever001](https://avatars.githubusercontent.com/u/1317919?v=4)](https://github.com/vever001 "vever001 (9 commits)")

### Embed Badge

![Health badge](/badges/vever001-composer-installers-dir/health.svg)

```
[![Health](https://phpackages.com/badges/vever001-composer-installers-dir/health.svg)](https://phpackages.com/packages/vever001-composer-installers-dir)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)