I got the following trying to install the module with composer:
# composer require drupal/ui_patterns_field_group:^2.0
./composer.json has been updated
Running composer update drupal/ui_patterns_field_group
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/ui_patterns_field_group ^2.0, found drupal/ui_patterns_field_group[dev-1.x, 1.0.0-beta1, ..., 1.x-dev (alias of dev-1.x)] but it does not match the constraint.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
composer require 'drupal/ui_patterns_field_group-ui_patterns_field_group:^2.0@alpha'
For some reason the package name is "drupal/ui_patterns_field_group-ui_patterns_field_group" as shown in the release information:
# composer require 'drupal/ui_patterns_field_group-ui_patterns_field_group:^2.0'
./composer.json has been updated
Running composer update drupal/ui_patterns_field_group-ui_patterns_field_group
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 0 updates, 0 removals
- Locking drupal/ui_patterns_field_group-ui_patterns_field_group (2.0.0-alpha2)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 0 updates, 0 removals
No patches supplied.
Gathering patches for dependencies. This might take a minute.
- Installing drupal/ui_patterns_field_group-ui_patterns_field_group (2.0.0-alpha2): Extracting archive
Generating autoload files
54 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Found 1 security vulnerability advisory affecting 1 package.
Run "composer audit" for a full list of advisories.
drupal/ui_patterns_field_group-ui_patterns_field_group is not the expected package name for this project. Also, the installation directory is modules/contrib/ui_patterns_field_group-ui_patterns_field_group
Active
2.0
Miscellaneous
Hi @manuel.adan!
Thank you for reporting this.
I am aware of that issue and I filled a request on the appropriate issue queue to get this fixed:
💬
Extracting a submodule in its own module
Active
While it's really unexpected and not ideal, it doesn't prevent the module from working.
I hope this is going to be fixed soon but in the meantime there is nothing we can do.