Skip to content

Run composer on the host, not in the sandbox - #342

Merged
AydinHassan merged 1 commit into
masterfrom
composer-on-host
Nov 1, 2026
Merged

AydinHassan merged 1 commit into
masterfrom
composer-on-host

Conversation

@AydinHassan

Copy link
Copy Markdown
Member

Step 1 of the simpler plan for #336: every sandbox run should be the same, so composer moves out of it.

  • New Composer class runs composer on this machine, always with --no-plugins --no-scripts, so no package code runs.
  • PrepareSolutionListener and ReferencePackages use it. warm() now fills this machine's composer cache.
  • DockerSandbox loses its composer handling, the composer cache volume and vendorVolumes (Let DockerSandbox keep vendor in a volume for listed folders #340). vendor is just part of the solution again, so ComposerCheck works as it always did.

Checked with learn-you-php dependency-heaven verify, SANDBOX=docker.

Package plugins and scripts never run, so no package code does. vendor is then just another file of the solution, so DockerSandbox drops its composer handling, the composer cache volume and vendorVolumes.
@AydinHassan
AydinHassan merged commit 6b9478c into master Nov 1, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant