Download the PHP package grasmash/composerize-drupal without Composer
On this page you can find all versions of the php package grasmash/composerize-drupal. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download grasmash/composerize-drupal
More information about grasmash/composerize-drupal
Files in grasmash/composerize-drupal
Package composerize-drupal
Short Description Convert a non-Composer managed Drupal application into a Composer-managed application.
License
Informations about the package composerize-drupal
Composerize Drupal
Composerize Drupal is a Composer plugin that converts a non-Composer-managed Drupal application (e.g., one created via tarball) to a Composer-managed Drupal application.
It is not for creating new Drupal applications. If you want to create a brand new Drupal application, use drupal-project instead.
Functionality
The composerize-drupal
command will perform the following operations:
- Remove all vestigial
composer.json
andcomposer.lock
files - Generate a new
composer.json
in the[composer-root]
directory based on template.composer.json.- Populate
require
with entries fordrupal/core-recommended
anddrupal/core-composer-scaffold
- Populate
require
with an entry for each project in:[drupal-root]/modules
[drupal-root]/modules/contrib
[drupal-root]/themes/contrib
[drupal-root]/profiles/contrib
- Require and configure suggested Composer plugins:
- Add
drupal/composer-scaffold
file paths toextra
configuration to ensure that Drupal projects are downloaded to the correct locations. - Create and populate
extra.patches
object to facilitate patching with Composer Patches. Patches to profiles, themes, and modules will be automatically discovered and moved to the a new [repo-root]/patches directory. - Add entries to
repositories
:https://packages.drupal.org/8
for installing packages from Drupal.orghttps://asset-packagist.org/
to permit installing NPM packages.
- Add
- Populate
- Create or modify
[composer-root]/.gitignore
with entries for Composer-managed contributed projects as per best practices. You can modify.gitignore
after composerization if you'd prefer not to follow this practice. - Execute
composer update
to generatecomposer.lock
, autoload files, and install all dependencies in the correct locations.
It will NOT add any contributed projects in docroot/libraries
to composer.json
. You must add those to your composer.json
file manually. In addition to packagist and Drupal.org packages, you may also use any package from asset packagist, which makes NPM packages available to Composer.
Installation
Usage:
The [composer-root]
should be the root directory of your project, where .git
is located.
The [drupal-root]
should be the Drupal root, where index.php
is located.
Examples:
Options
--composer-root
: Specifies the root directory of your project wherecomposer.json
will be generated. This should be the root of your Git repository, where.git
is located.--drupal-root
: Specifies the Drupal root directory whereindex.php
is located.--no-update
: Preventscomposer update
from being automatically run aftercomposer.json
is generated.--no-gitignore
: Prevents modification of the root .gitignore file.--exact-versions
: Will cause Drupal core and contributed projects (modules, themes, profiles) to be be required with exact verions constraints incomposer.json
, rather than using the default caret operator. E.g., adrupal/core
would be required as8.4.4
rather than^8.4.4
. This prevents projects from being updated. It is not recommended as a long-term solution, but may help you convert to using Composer more easily by reducing the size of the change to your project.
All versions of composerize-drupal with dependencies
composer-plugin-api Version ^2.0
composer/semver Version ^3
symfony/finder Version ^3.4
symfony/yaml Version ^3.4
webflo/drupal-finder Version ^1.1
webmozart/path-util Version ^2.3