- Issue created by @batigolix
- 🇮🇳India vishal.kadam Mumbai
Projects with releases cannot be deleted.
Regarding your issue, it seems your Drupal core’s composer.json file has the minimum-stability set to stable. Try changing it to dev and see if it resolves the problem.
- 🇳🇱Netherlands batigolix Utrecht
Where did you see my core composer json file?
- 🇺🇸United States cmlara
@vishal.kadam this is a well known issue on D.O that has nothing to do with stability levels.
@batigolix 🌱 Change how modules and submodule dependencies are handled to have more consistent namepsaces [DRAFT]. Active has some related discussions about a long term fix for this (though there appears to be no movement to resolve this long term).
The short version is the MOM project (likely) now has control of the namespace as it had a project with that module name first.
You can move this to Drupal infrastructure and ask them to rename, no gurantee they will, however they have in the past.
- 🇳🇱Netherlands batigolix Utrecht
I updated the description and move this to the Infrastructure queue.
Thanks @cmlara & vishal for your help.
- 🇺🇸United States drumm NY, US
This is working as designed to disambiguate components in modules, since Composer resolves dependencies on the project level, and Drupal also handles dependencies among sub-modules and other components within a single project. Composer namespaces do not always equal project names.
Using the Composer command exactly as on the release and project page,
composer require 'drupal/matomo_onpage_metrics-matomo_onpage_metrics:^1.0@beta'
does work as expected.