PHPackages auroro/workspaces - 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. auroro/workspaces ActiveComposer-plugin[Utility & Helpers](/categories/utility) auroro/workspaces ================= Composer plugin for PHP monorepo workspace management — cascading installs, dependency graph, filtering, and cross-worktree linking v0.5.1(1mo ago)01MITPHPPHP >=8.3 Since Mar 15Pushed 1mo agoCompare [ Source](https://github.com/next-press/workspaces)[ Packagist](https://packagist.org/packages/auroro/workspaces)[ RSS](/packages/auroro-workspaces/feed)WikiDiscussions main Synced 3w ago READMEChangelogDependencies (14)Versions (12)Used By (0) Auroro Workspaces ================= [](#auroro-workspaces) Composer plugin for PHP monorepo workspace management. Part of the Auroro framework ecosystem. Handles cascading installs with symlinked vendors, dependency-aware parallel command execution, dependency graph generation, and cross-worktree package linking. Installation ------------ [](#installation) ``` composer require auroro/workspaces ``` Configuration ------------- [](#configuration) Add workspace paths to your root `composer.json`: ``` { "extra": { "workspaces": { "paths": ["packages/*", "apps/*"] } }, "config": { "allow-plugins": { "auroro/workspaces": true } } } ``` The `paths` array defines glob patterns for workspace package directories. Defaults to `["packages/*"]` if omitted. ### Options [](#options) KeyTypeDefaultDescription`paths``list``["packages/*"]`Glob patterns for workspace package directories`graph``string|null``null`Path to write the dependency graph (relative to root)`autolink``bool``false`Automatically link/unlink packages on install/uninstall### Dependency graph output [](#dependency-graph-output) ``` { "extra": { "workspaces": { "paths": ["packages/*", "apps/*"], "graph": ".github/workspace.json" } } } ``` The graph is always written to `vendor/workspace.json`. The `graph` option writes an additional copy to the specified path (relative to the project root). ### Automatic linking [](#automatic-linking) By default, the plugin does **not** automatically link or unlink workspace packages. This means you must run `composer link` manually after installing to register packages as path repositories in Composer's global config. To have this happen automatically on `composer install` and `composer uninstall`, set `autolink` to `true`: ``` { "extra": { "workspaces": { "paths": ["packages/*", "apps/*"], "autolink": true } } } ``` You can always link/unlink manually with `composer link` and `composer unlink` regardless of this setting. What happens on `composer install` ---------------------------------- [](#what-happens-on-composer-install) Two things happen automatically after every `composer install` or `composer update`: 1. **Dependency graph** — scans all workspace packages, builds an internal dependency graph, and writes it to `vendor/workspace.json` (and to the configured `graph` path if set). 2. **Cascading vendor install** — for workspace packages that have a `bin` entry or a `composer.lock`, creates a `vendor/` directory with symlinks to root vendor packages, copies Composer metadata and bin proxies, then runs `composer dump-autoload` in parallel. No duplicate downloads — everything points back to the root vendor. If `autolink` is enabled, workspace linking also runs automatically (see above). Commands -------- [](#commands) ### `composer each ` [](#composer-each-script) Run a Composer script defined in each workspace package's `composer.json`. Packages that don't define the script are skipped. ``` composer each test # run "test" script in all packages that define it composer each build # run "build" script ``` ### `composer each -- ` [](#composer-each----command) Run an arbitrary shell command in every workspace package directory. ``` composer each -- ls -la # list files in each package composer each -- git status # check git status per package ``` ### Filtering [](#filtering) Use `--filter` / `-f` to select packages by glob pattern. Patterns match the short name (after `/`) by default. Include `/` in the pattern to match the full package name. ``` composer each --filter 'phpx*' test # packages matching phpx* composer each --filter '*' --filter '!docs' test # all except docs composer each -f 'auroro/cl*' -- echo hello # full name matching ``` Prefix with `!` to exclude. ### Execution order [](#execution-order) Commands run in **topological levels** — packages at the same dependency level execute in parallel, but each level waits for the previous one to complete. This ensures dependencies are always satisfied before dependents run. ### `composer link` [](#composer-link) Manually re-link the current worktree's packages to Composer's global config. This happens automatically on install, but can be run explicitly after switching worktrees. ### `composer unlink [--all]` [](#composer-unlink---all) Remove the current worktree's entries from global config. Use `--all` to remove all worktrees for the monorepo. ### `composer workspaces` [](#composer-workspaces) Show all linked worktrees for the monorepo, highlighting the current one. Dependency graph ---------------- [](#dependency-graph) Written to `vendor/workspace.json` on every install/update (and to the `graph` path if configured): ``` { "packages": { "auroro/result": { "path": "packages/result", "dependencies": [] }, "auroro/bus": { "path": "packages/bus", "dependencies": ["auroro/result"] } }, "topological_levels": [ ["auroro/code", "auroro/epoch", "auroro/result"], ["auroro/bus", "auroro/schema"], ["auroro/clip", "auroro/capsule"] ] } ``` Each level contains packages that can be processed in parallel. Levels are ordered so that all dependencies of level N appear in levels 0..N-1. Cascading vendor install ------------------------ [](#cascading-vendor-install) Workspace packages with a `bin` entry or `composer.lock` get their own `vendor/` directory automatically: - Package directories are **symlinked** from root vendor (no disk duplication) - Composer's `installed.php` and `installed.json` are copied for autoloader generation - Bin proxies are **copied** (not symlinked) so `__DIR__` resolves to the workspace's own vendor - `composer dump-autoload` runs in parallel for all workspaces This means `apps/skeleton/vendor/bin/phpx` works exactly as if you ran `composer install` in that directory — but without downloading anything twice. Cross-worktree linking ---------------------- [](#cross-worktree-linking) When working with multiple git worktrees of the same monorepo, each worktree can link its packages to Composer's global config. This makes workspace packages available as path repositories to any Composer project on the machine. ``` # In worktree auroro/main composer link # registers packages/* as path repos # In worktree auroro/feature-x composer link # also registers its packages/* # Both are now available — Composer resolves from whichever matches composer workspaces # shows all linked worktrees ``` Global config is stored in `~/.composer/config.json` (or `$XDG_CONFIG_HOME/composer/config.json`). ### Health Score 38 — LowBetter than 83% of packages Maintenance93 Actively maintained with recent releases Popularity1 Limited adoption so far Community6 Small or concentrated contributor base Maturity45 Maturing project, gaining track record 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 ~6 days Recently: every ~16 days Total 11 Last Release 36d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/4679684?v=4)[Arindo Duque](/maintainers/aanduque)[@aanduque](https://github.com/aanduque) --- Top Contributors [![aanduque](https://avatars.githubusercontent.com/u/4679684?v=4)](https://github.com/aanduque "aanduque (1 commits)") ### Code Quality TestsPest Static AnalysisPHPStan Code StylePHP CS Fixer Type Coverage Yes ### Embed Badge ![Health badge](/badges/auroro-workspaces/health.svg) ``` [![Health](https://phpackages.com/badges/auroro-workspaces/health.svg)](https://phpackages.com/packages/auroro-workspaces) ``` ### Alternatives [symfony/runtime Enables decoupling PHP applications from global state 74694.9M938](/packages/symfony-runtime)[ergebnis/composer-normalize Provides a composer plugin for normalizing composer.json. 1.1k40.0M2.6k](/packages/ergebnis-composer-normalize)[drupal/core-composer-scaffold A flexible Composer project scaffold builder. 5344.1M526](/packages/drupal-core-composer-scaffold)[drupal/core-project-message Adds a message after Composer installation. 2124.0M193](/packages/drupal-core-project-message)[sandersander/composer-link Adds ability to link local packages for development with composer 94441.4k](/packages/sandersander-composer-link)[phpro/grumphp-shim GrumPHP Phar distribution 284.6M333](/packages/phpro-grumphp-shim) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)