Composer is fetching drupal/ckeditorselectall instead of requested drupal/ckeditor_selectall package

Confirmed:

curl -s https://packages.drupal.org/files/packages/8/p2/drupal/ckeditor_selectall.json |jq -r '.packages["drupal/ckeditor_selectall"][0].homepage'

https://www.drupal.org/project/ckeditorselectall

Belongs to p.d.o though.

https://www.drupal.org/project/ckeditor_selectall → has no releases, so is not installable with Composer.

ckeditorselectall is a project containing ckeditor_selectall module. Composer is designed to only do project dependencies (ckeditorselectall), but Drupal core works with module dependencies (ckeditor_selectall). So packages.drupal.org uses Composer metapackages to make dependencies available via the module name, which eased the transition to Composer when namespacing the Drupal dependencies with project & module name was less common.

If ckeditor_selectall creates a release in the future, it will have a different Composer namespace, so ckeditor_selectall's current behavior in Composer is not changed. We wouldn't want to allow that since it would change what code sites get. Composer namespaces do not always match up to the project name.

From https://git.drupalcode.org/project/ckeditor_selectall/-/blob/8.x-1.x/src... (25th March 2019)

namespace Drupal\ckeditor_selectall\Plugin\CKEditorPlugin;

also from https://git.drupalcode.org/project/ckeditorselectall/-/blob/1.0.x/ckedit... (25th July 2023)

namespace Drupal\ckeditor_selectall\Plugin\CKEditorPlugin;

Perhaps there could be some community monitoring of namespaces.