Thanks for using this Drupal component.
You can participate in its development on Drupal.org, through our issue system: https://www.drupal.org/project/issues/drupal
You can get the full Drupal repo here: https://www.drupal.org/project/drupal/git-instructions
You can browse the full Drupal repo here: https://git.drupalcode.org/project/drupal
The Recipe Unpacking system is a Composer plugin that manages "drupal-recipe"
packages. Recipes are special Composer packages designed to bootstrap Drupal
projects with necessary dependencies. When a recipe is installed, this plugin
"unpacks" it by moving the recipe's dependencies directly into your project's
root composer.json, and removes the recipe as a project dependency.
A recipe is a Composer package with type drupal-recipe that contains a curated
set of dependencies, configuration and content but no code of its own. Recipes
are meant to be "unpacked" and "applied" rather than remain as runtime
dependencies.
Unpacking is the process where:
- A recipe's dependencies are added to your project's root
composer.json - The recipe itself is removed from your dependencies
- The
composer.lockand vendor installation files are updated accordingly - The recipe will remain in the project's recipes folder so it can be applied
Unpack a recipe package that's already required in your project.
composer drupal:recipe-unpack drupal/example_recipeUnpack all recipes that are required in your project.
composer drupal:recipe-unpackThis command doesn't take additional options.
By default, recipes are automatically unpacked after running composer require
for a recipe package:
composer require drupal/example_recipeThis will:
- Download the recipe and its dependencies
- Add the recipe's dependencies to your project's root
composer.json - Remove the recipe itself from your dependencies
- Update your
composer.lockfile
Recipes are always automatically unpacked when creating a new project from a template that requires this plugin:
composer create-project drupal/recommended-project my-projectAny recipes included in the project template will be unpacked during installation, as long as the plugin is enabled.
Configuration options are set in the extra section of your composer.json
file:
{
"extra": {
"drupal-recipe-unpack": {
"ignore": ["drupal/recipe_to_ignore"],
"on-require": true
}
}
}| Option | Type | Default | Description |
|---|---|---|---|
ignore |
array | [] |
List of recipe packages to exclude from unpacking |
on-require |
boolean | true |
Automatically unpack recipes when required by composer require |
- The system identifies packages of type
drupal-recipeduring installation - For each recipe not in the ignore list, it:
- Extracts its dependencies
- Adds them to the root
composer.json - Recursively processes any dependencies that are also recipes
- Removes the recipe and any dependencies that are also recipes from the root
composer.json
- Updates all necessary Composer files:
composer.jsoncomposer.lockvendor/composer/installed.jsonvendor/composer/installed.php
Recipes will not be unpacked in the following scenarios:
-
Explicit Ignore List: If the recipe is listed in the
ignorearray in yourextra.drupal-recipe-unpackconfiguration{ "extra": { "drupal-recipe-unpack": { "ignore": ["drupal/recipe_name"] } } } -
Disabled Automatic Unpacking: If
on-requireis set tofalsein yourextra.drupal-recipe-unpackconfiguration{ "extra": { "drupal-recipe-unpack": { "on-require": false } } } -
Development Dependencies: Recipes in the
require-devsection are not automatically unpacked{ "require-dev": { "drupal/dev_recipe": "^1.0" } }You will need to manually unpack these using the
drupal:recipe-unpackcommand if desired. -
With
--no-installOption: When usingcomposer requirewith the--no-installflagcomposer require drupal/example_recipe --no-install
In this case, you'll need to run
composer installafterward and then manually unpack using thedrupal:recipe-unpackcommand.
# This will automatically install and unpack the recipe
composer require drupal/example_recipeThe result:
- Dependencies from
drupal/example_recipeare added to your rootcomposer.json drupal/example_recipeitself is removed from your dependencies- You'll see a message: "drupal/example_recipe unpacked successfully."
- The recipe files will be present in the drupal-recipe installer path
# First require the recipe without unpacking
composer require drupal/example_recipe --no-install
composer install
# Then manually unpack it
composer drupal:recipe-unpack drupal/example_recipe# This won't automatically unpack (dev dependencies aren't auto-unpacked)
composer require --dev drupal/dev_recipe
# You'll need to manually unpack if desired (with confirmation prompt)
composer drupal:recipe-unpack drupal/dev_recipecomposer create-project drupal/recipe-based-project my-projectAny recipes included in the project template will be automatically unpacked during installation.
-
Review Recipe Contents: Before requiring a recipe, review its dependencies to understand what will be added to your project.
-
Consider Versioning: When a recipe is unpacked, its version constraints for dependencies are merged with your existing constraints, which may result in complex version requirements.
-
Dev Dependencies: Be cautious when unpacking development recipes, as their dependencies will be moved to the main
requiresection, notrequire-dev. -
Custom Recipes: When creating custom recipes, ensure they have the correct package type
drupal-recipeand include appropriate dependencies.
- Check if the package type is
drupal-recipe - Verify it's not in your ignore list
- Confirm it's not in
require-dev(which requires manual unpacking) - Ensure you haven't used the
--no-installflag without following up with installation and manual unpacking
If you encounter issues during unpacking:
- Check Composer's error output for specific issues and run commands with the
--verboseflag - Verify that version constraints between your existing dependencies and the recipe's dependencies are compatible
- For manual troubleshooting, consider temporarily setting
on-requiretofalseand unpacking recipes one by one