PHPackages                             wireframe-framework/processwire-composer-installer - 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. [Framework](/categories/framework)
4. /
5. wireframe-framework/processwire-composer-installer

ActiveComposer-plugin[Framework](/categories/framework)

wireframe-framework/processwire-composer-installer
==================================================

Custom Composer installer for the ProcessWire CMS/CMF modules and site profiles.

1.1.1(3y ago)510.0k↓21.2%20MPL-2.0PHP

Since Jun 2Pushed 3y ago1 watchersCompare

[ Source](https://github.com/wireframe-framework/processwire-composer-installer)[ Packagist](https://packagist.org/packages/wireframe-framework/processwire-composer-installer)[ Docs](https://wireframe-framework.com/docs/processwire-composer-installer/)[ RSS](/packages/wireframe-framework-processwire-composer-installer/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (10)Dependencies (2)Versions (16)Used By (20)

ProcessWire Composer Installer
==============================

[](#processwire-composer-installer)

This project contains [Composer custom installers](https://getcomposer.org/doc/articles/custom-installers.md) for ProcessWire CMS/CMF modules and site profiles.

What does it do and why do we need it?
--------------------------------------

[](#what-does-it-do-and-why-do-we-need-it)

By default Composer installs all packages into the /vendor/ directory. This is great for things that support this type of structure, but not so great for projects – such as ProcessWire – that expect things to be in specific location: modules in /site/modules/module-name/, and site profiles generally as the /site/ directory itself, /site-profile-name/ when the system hasn't been installed yet, or before installat/site-subsite-name/ in the case of native multisite support.

ProcessWire Composer Installer currently makes two "corrections" to packages that define it as a dependency in their composer.json files:

- **modules** are installed under `./site/modules/ModuleName/` (module name is read from composer.json and converted to PascalCase)
- **site profiles** are installed under `./site-profile-name/` (site profile name is read from composer.json and the site- prefix is added automatically if needed)

Site-specific modules supports
------------------------------

[](#site-specific-modules-supports)

One more thing to note is that modules can be installed either from the root directory of the ProcessWire installation, or from the `/site/` directory itself. Installer will automatically determine which location you're currently in, and adjust paths accordingly.

This way we can install modules on a per-site basis (in the case of multisite), or include Composer based module dependencies with a site profile (which would otherwise require manual modifications to the ProcessWire root directory composer.json file, or at least running `composer require` in the root directory for said dependencies.)

Alternatively...
----------------

[](#alternatively)

There's a very similar project you might've heard of, called `hari/pw-module`. While this project and Hari's ProcessWire module installer are similar, there are a few key differences:

- This project allows you to install both modules *and* site profiles
- This project allows you to install modules from the /site/ directory
- This project provides some additional features (and composer.json options) in terms of module and site profile naming, and also includes additional rules for auto-formatting module and site profile directory names

Usage
-----

[](#usage)

### For developers installing modules or site profiles

[](#for-developers-installing-modules-or-site-profiles)

- To add a new module from Packagist, run `composer require vendor-name/module-name` in either ProcessWire root directory, or your /site/ directory.
- To add a new site profile from Packagist, run `composer require vendor-name/site-profile-name` in the ProcessWire root directory.

*Note that in order for this work, the module or site profile in question has to have `wireframe-framework/processwire-composer-installer` as a dependency. See next section for instructions for module or site profile authors.*

#### Customizing installer paths

[](#customizing-installer-paths)

By default site profiles are installed under current working directory, and modules under site/modules/ (or modules/ in case you're already in a site directory). You can, though, override the default paths in the root composer.json of your project:

```
{
  "require": {
    ...
  },
  "extra": {
    "pw-module-path": "site/modules",
    "pw-site-profile-path": "",
  }
}

```

### For module or site profile authors

[](#for-module-or-site-profile-authors)

The usage of this project is rather simple. You just need to a) add `wireframe-framework/processwire-composer-installer` as a dependency to your project by manually modifying the composer.json file or by running `composer require wireframe-framework/processwire-composer-installer` in your module or site profile root directory, and b) define the type of your package (via composer.json) as `pw-module` (for modules) or `pw-site-profile` (for site profiles).

Here's a stripped-down sample composer.json for a module:

```
{
    "name": "vendor-name/module-name",
    "type": "pw-module",
    "require": {
        "wireframe-framework/processwire-composer-installer": "^1.0.0"
    }
}

```

And here's an equally stripped-down sample composer.json for a site profile:

```
{
    "name": "vendor-name/site-profile-name",
    "type": "pw-site-profile",
    "require": {
        "wireframe-framework/processwire-composer-installer": "^1.0.0"
    }
}

```

*In order for your modules to be easily installed, you should also add them to Packagist: .*

Requirements
------------

[](#requirements)

- PHP 5.5 or newer

### Why does this project require other installers via composer.json?

[](#why-does-this-project-require-other-installers-via-composerjson)

In case you're wondering why we currently have hari/pw-module as a requirement for this package, there's actually a good reason for this, even though it is admittedly a bit of a hack:

- Composer doesn't let us define package install order, but it prioritizes Composer installers.
- If multiple installers compete for one package, the installer installed or loaded later wins.

By adding other installers (currently only hari/pw-module) as a dependency for this project we're actually effectively forcing Composer to install it *before* this project, which in turn allows us to override other installers when it comes to choosing an installer for pw-\* packages.

License
-------

[](#license)

This project is licensed under the Mozilla Public License Version 2.0.

###  Health Score

37

—

LowBetter than 83% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity29

Limited adoption so far

Community21

Small or concentrated contributor base

Maturity67

Established project with proven stability

 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.

###  Release Activity

Cadence

Every ~91 days

Recently: every ~264 days

Total

13

Last Release

1446d ago

Major Versions

0.1.0 → 1.0.02019-06-29

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/1252021?v=4)[Teppo Koivula](/maintainers/teppokoivula)[@teppokoivula](https://github.com/teppokoivula)

---

Top Contributors

[![teppokoivula](https://avatars.githubusercontent.com/u/1252021?v=4)](https://github.com/teppokoivula "teppokoivula (17 commits)")

---

Tags

composerinstallerprocesswire

### Embed Badge

![Health badge](/badges/wireframe-framework-processwire-composer-installer/health.svg)

```
[![Health](https://phpackages.com/badges/wireframe-framework-processwire-composer-installer/health.svg)](https://phpackages.com/packages/wireframe-framework-processwire-composer-installer)
```

###  Alternatives

[composer/installers

A multi-framework Composer library installer

1.4k136.0M6.0k](/packages/composer-installers)[dealerdirect/phpcodesniffer-composer-installer

PHP\_CodeSniffer Standards Composer Installer Plugin

598161.9M1.9k](/packages/dealerdirect-phpcodesniffer-composer-installer)[yiisoft/yii2-composer

The composer plugin for Yii extension installer

8628.8M55](/packages/yiisoft-yii2-composer)[processwire/processwire

ProcessWire CMS/CMF

1.1k32.9k28](/packages/processwire-processwire)[yiisoft/config

Composer plugin and a library for config assembling

34368.9k27](/packages/yiisoft-config)[craftcms/plugin-installer

Craft CMS Plugin Installer

283.3M4](/packages/craftcms-plugin-installer)

PHPackages © 2026

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