Contrib.social

RecipeActivator needs to handle unpacked recipes that aren't Composer-managed

Open on Drupal.org →
Created on 30 May 2025, 24 days ago

Problem/Motivation

Core now has a recipe unpacking plugin which moves a recipe's dependencies into the top-level composer.json at require time, and then removes the recipe from Composer's jurisdiction. The recipe is still physically there, but Composer no longer knows about it. That's a problem, because RecipeActivator relies on Composer to tell it where a given recipe is installed.

Proposed resolution

RecipeActivator should first ask Composer about where a recipe is installed, and if Composer doesn't know, it should try to compute the path based on what can be read from composer.json.

🐛 Bug report
Status

Active

Version

2.1

Component

Code

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024