How can I force composer to install modules in app/code instead of vendor directory in Magento 2?
I have few modules they strictly need to be install in app/code, but when I update them with composer, they install in vendor directory.
Magento – How to install modules in app/code with composer in Magento 2
composermagento2module
Related Solutions
Maybe my code can be useful for you (tested in the observer):
/**
* @var \Magento\Framework\App\DeploymentConfig
*/
protected $deploymentConfig;
/**
* @var \Magento\Framework\Component\ComponentRegistrarInterface
*/
protected $componentRegistrar;
/**
* @var \Magento\Framework\Filesystem\Directory\ReadFactory
*/
protected $readFactory;
/**
* @param \Magento\Framework\App\DeploymentConfig $deploymentConfig
* @param \Magento\Framework\Component\ComponentRegistrarInterface $componentRegistrar
* @param \Magento\Framework\Filesystem\Directory\ReadFactory $readFactory
*/
public function __construct(
\Magento\Framework\App\DeploymentConfig $deploymentConfig,
\Magento\Framework\Component\ComponentRegistrarInterface $componentRegistrar,
\Magento\Framework\Filesystem\Directory\ReadFactory $readFactory
) {
$this->deploymentConfig = $deploymentConfig;
$this->componentRegistrar = $componentRegistrar;
$this->readFactory = $readFactory;
}
/**
* Get module composer version
*
* @param $moduleName
* @return \Magento\Framework\Phrase|string|void
*/
public function getModuleVersion($moduleName)
{
$path = $this->componentRegistrar->getPath(
\Magento\Framework\Component\ComponentRegistrar::MODULE,
$moduleName
);
$directoryRead = $this->readFactory->create($path);
$composerJsonData = $directoryRead->readFile('composer.json');
$data = json_decode($composerJsonData);
return !empty($data->version) ? $data->version : __('Read error!');
}
/**
* Collect enabled modules version
*
* @param Observer $observer
*/
public function execute(Observer $observer)
{
$modules = $this->deploymentConfig->get('modules');
$modulesWithVersion = [];
foreach ($modules as $moduleName => $isEnabled) {
if (!$isEnabled) {
continue;
}
$modulesWithVersion[$moduleName] = $this->getModuleVersion($moduleName);
}
}
- Collects all enabled module names from the config
- Reads their
composer.jsonone-by-one and saves version
Result (in debug):
Yes you would commit both the composer.json and composer.lock files.
As part of your deployment process to the live environment you would need to run composer install - this takes the information stored in the composer.lock file and recreates the very same versions you had installed locally.
Best Answer
I'm answering my own question, so it will be beneficial for someone else later,
To be able to install in a custom path, your module must support
composer/installersso add it to your module'srequiresection, eg:and then give your module a custom path in
extrasection, where you want it to be installed. Eg:and your module type must be
"type": "magento-library"not"type": "magento2-module"(don't worry changing the type will not break anything, it'll still work like before)so the complete json for the module will be like something this
and just to be sure, add it to your main
composer.json's extra section too, this maybe optional but I have added it anyway.Then run
composer update, so it will install your module inapp/codeor your given path.