joachim-n / drupal-core-development-project Goto Github PK

View Code? Open in Web Editor NEW

39.0 39.0 11.0 58 KB

Project template for developing Drupal core with a git clone.

PHP 100.00%

drupal-core-development-project's People

Contributors

Stargazers

Watchers

Forkers

shaal knibals andy-blum bbrala thelebster bhanu951 pyrello rfay darrenoh rpkoller markfullmer

drupal-core-development-project's Issues

Update dependencies for Drupal 10

I believe composer/installers and symfony/var-dumper need to have their version requirements bumped to support Drupal 10:

"composer/installers": "^2.0",
"symfony/var-dumper": "^6.2"

-mike

Fix installation profiles and libraries not working

The install script is in a symlinked directory, so using __DIR__ drops into the repos/drupal path, from where contrib installation profiles cannot be found. I think we need to symlink the profiles/contrib directory into repos/drupal the way we do with the vendor directory.
The DRUPAL_ROOT constant also uses __DIR__, so any code relying on DRUPAL_ROOT, such as code looking for the libraries folder, breaks if folders are not symlinked into repos/drupal.

Install command results in error

Running the composer create-project command from https://github.com/joachim-n/drupal-core-development-project#installation results in the following error:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/core-recommended * -> satisfiable by drupal/core-recommended[11.x-dev].
    - drupal/core-recommended 11.x-dev requires drupal/core 10.2.x-dev -> found drupal/core[11.x-dev] but it does not match the constraint.

I had previously installed this project with no issues and was in the process of re-installing after removing the previous installation.

[drush] Uncaught Exception: Could not locate autoload.php when `vendor/` folder is symlinked

When executing any drush command, I get this weird exception:
Uncaught Exception: Could not locate autoload.php. cwd is /var/www/html; __DIR__ is /var/www/html/web/vendor/drush/drush

Specifically I'm using:
Host setup : DDEV 1.19
Drupal version : 9.4.0-dev
Drush version : 10.6.2
Drush script : /var/www/html/vendor/bin/drush

When using Xdebug, I can see in order:

vendor/bin/drush is executed
vendor/drush/drush/drush is executed
vendor/drush/drush/drush.php is executed. And vendor/autoload.php is found
then during executing the command **web/**vendor/drush/drush/drush.php is called, and the autoload.php is not found for some reason.

This is either when I execute drush or vendor/bin/drush or vendor/drush/drush/drush, always from the root of the project /var/www/html.

contrib modules can't be installed by Composer if core is on 11.x branch

Composer thinks that contrib module requiring ^10 can't be installed if core is on the 11.x branch.

DevelopmentProjectCommands Class conflicts for Drush 12

DevelopmentProjectCommands Class conflicts for Drush 12+ and produces below error when running any drush commands.


drush st
PHP Fatal error:  Class Drush\Commands\core_development\DevelopmentProjectCommands cannot extend final class Drush\Commands\core\CacheCommands in /var/www/html/drush/Commands/core_development/DevelopmentProjectCommands.php on line 0

Fatal error: Class Drush\Commands\core_development\DevelopmentProjectCommands cannot extend final class Drush\Commands\core\CacheCommands in /var/www/html/drush/Commands/core_development/DevelopmentProjectCommands.php on line 0
 [warning] Drush command terminated abnormally.

Current CacheCommands class is final in Drush Version 12+ Introduced in PR drush-ops/drush#5427

DRUPAL_ROOT value is the symlinked directory, instead of the project location

Describe the bug

When installing a Drupal website that is based on this project, DRUPAL_ROOT gets the wrong value - /var/www/html/repos/drupal.

To Reproduce

Install a Drupal website based on this project's setup.
using Xdebug, place a breakpoint in web/core/includes/bootstrap.inc, after the line where DRUPAL_ROOT gets value
define('DRUPAL_ROOT', dirname(__DIR__, 2));
Confirm that DRUPAL_ROOT gets the wrong value of repos/drupal instead of the directory where Drupal project is.

Expected behavior

I expect DRUPAL_ROOT to be set like a regular Drupal website (and not in `/repos/drupal')

Screenshots

Version and configuration information (please complete the following information)

Additional context

Contrib tests can not be executed

I would want to use drupal-core-development-project for contrib development too but currently I can not do that. Tests for contrib are failing. Core tests work ok.

Running

phpunit web/modules/contrib/devel

Gives error

Fatal error: Uncaught Error: Class "Drupal\Tests\devel_generate\Functional\DevelGenerateBrowserTestBase" not found in /var/www/web/modules/contrib/devel/devel_generate/tests/src/Functional/DevelGenerateBrowserTest.php:14

DevelopmentProjectCommands broken on Drush 12

AAAAAAAAAAAAAAAAAARRRRRGGGGGHHH. AGAIN. It's broken AGAIN.

The culprit this time is this line in Drush's ServiceManager which filters out command classes:

        // If a command class has a static `create` method, then we will
        // postpone instantiating it until after we bootstrap Drupal.
        $this->bootstrapCommandClasses = array_filter($commandClasses, [$this, 'hasStaticCreateFactory']);

Project does not work with core's 10.0.x branch

Installed per the instructions in the readme, and then switched to the 10.0.x branch. Kicked off a DDEV project with it and the project errors with:

Warning: require(/var/www/html/vendor/composer/../../web/core/includes/guzzle_php81_shim.php): Failed to open stream: No such file or directory in /var/www/html/vendor/composer/autoload_real.php on line 75

Fatal error: Uncaught Error: Failed opening required '/var/www/html/vendor/composer/../../web/core/includes/guzzle_php81_shim.php' (include_path='/var/www/html/vendor/pear/pear_exception:/var/www/html/vendor/pear/console_getopt:/var/www/html/vendor/pear/pear-core-minimal/src:/var/www/html/vendor/pear/archive_tar:.:/usr/share/php') in /var/www/html/vendor/composer/autoload_real.php:75 Stack trace: #0 /var/www/html/vendor/composer/autoload_real.php(65): composerRequirebe8a091bca0079a3222cb044f9050d36('6db5533840cb1ae...', '/var/www/html/v...') #1 /var/www/html/vendor/autoload.php(7): ComposerAutoloaderInitbe8a091bca0079a3222cb044f9050d36::getLoader() #2 /var/www/html/repos/drupal/autoload.php(14): require('/var/www/html/v...') #3 /var/www/html/repos/drupal/core/install.php(38): require_once('/var/www/html/r...') #4 {main} thrown in /var/www/html/vendor/composer/autoload_real.php on line 75

Adjust the install instructions for DDEV

Hi, your repo was mentioned on the #ddev-for-core-dev channel on the drupal slack. Since the current discussions there are about making the addon by justafish compatible with DDEV 1.22.7 and the upcoming 1.23.0 as well as the recent change in core switching from Yarn 1 to Yarn 4 requiring corepack i've tested an install of your composer template as well. There are a few stumbling blocks:

if you are trying to install drupal-core-development-project based on the current instructions in DDEV 1.22.7 the composer create step fails due to the unmet PHP requirements. I've created a PR with a quick intermediate fix setting PHP to version 8.3 and node to version 20
the next problem is that drupal 11 switched to yarn 4 recently https://www.drupal.org/project/drupal/issues/3109556 . according to the suggestion by @longwave over in ddev/ddev#5988 DDEV introduced a config item to enable corepack for DDEV ddev/ddev#6012 . So in DDEV 1.23.0 there will be a config setting that will be set to true per default if you are having a drupal11 based codebase with the new drupal project type. Problem is for the time being until 1.23.0 is released corepack has to be manually enabled with ddev . corepack enable . Maybe the best solution might be adding the following snippet to a projects config.yaml

hooks:
  post-start: 
    - exec: corepack enable

after a restart you then get 1.22.22 in the project root and 4.1.1 in repos/drupal/core. the only downside in ddev 1.22.7 you get a prompt requiring to download yarn after every restart. that will be improved and not required anymore in DDEV 1.23.0

talking of DDEV 1.23.0 . there is one problem you have to have on your radar. ddev 1.23.0 will have a new drupal project type. on ddev config ddev DDEV will auto determine based on the codebase available which version of drupal is installed. problem with the steps for setting up your project, same as the quickstart guides on https://ddev.readthedocs.io/en/latest/users/quickstart/#drupal, on an empty directory where ddev composer create is run afterwards, ddev is unable to determine the exact version of drupal, therefore it is falling back to the default values (php 8.2 and corepack_enable false) which reintroduces the problems outlined in 1 and 2. it is a known problem and i'll open up an issue over in the ddev repo. there are also pitfalls upgrading from the drupal10 project type to the new drupal one which will be also covered in the aforementioned issue . it is just an fyi for now since there is only an alpha1 for 1.23.0 out

update: i've opened an issue about the problems outlined in point 3 ddev/ddev#6035

Dependency conflicts of Drupal core 8.9.x and var-dumper:^5.1

This line in composer.json gives me trouble...
https://github.com/joachim-n/drupal-core-development-project/blob/main/composer.json#L39

"symfony/var-dumper": "^5.1"

Steps to replicate -

cd repos/drupal
git checkout 8.9.x
composer update

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/core * -> satisfiable by drupal/core[8.9.x-dev].
    - Conclusion: don't install symfony/console v3.4.11 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper 5.3.x-dev (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.12 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper 5.4.x-dev (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.13 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.0-BETA1 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.14 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.0-BETA1 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.15 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.0-BETA2 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.16 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.0-BETA3 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.17 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.3.0-BETA1 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.18 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.3.0-BETA2 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.19 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.3.0-BETA3 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.20 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.0-RC1 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.21 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.0-RC2 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.22 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.0-RC1 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.23 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.0-RC2 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.24 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.3.0-RC1 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.25 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.0 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.26 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.1 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.27 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.2 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.28 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.3 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.29 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.4 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.30 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.5 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.31 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.6 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.32 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.7 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.33 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.8 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.34 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.9 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.35 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.10 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.36 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.1.11 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.37 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.0 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.38 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.1 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.39 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.2 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.40 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.3 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.41 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.4 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.42 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.5 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.43 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.6 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.44 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.7 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.45 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.8 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.46 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.2.10 (conflict analysis result)
    - Conclusion: don't install symfony/console v3.4.47 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper v5.3.0 (conflict analysis result)
    - Conclusion: don't install symfony/var-dumper 5.2.x-dev (conflict analysis result)
    - drupal/core 8.9.x-dev requires symfony/console ~3.4.0 -> satisfiable by symfony/console[v3.4.0-BETA1, ..., 3.4.x-dev].
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.10.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.9.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.8.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.7.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.6.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.5.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.4.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.3.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.2.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.1.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.0.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.0-RC2.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.0-RC1.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.0-BETA4.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.0-BETA3.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.0-BETA2.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console v3.4.0-BETA1.
    - symfony/var-dumper 5.1.x-dev conflicts with symfony/console 3.4.x-dev.
    - Root composer.json requires symfony/var-dumper ^5.1 -> satisfiable by symfony/var-dumper[v5.1.0-BETA1, ..., 5.4.x-dev].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

ComposerProjectTemplatesTest.php doesn't work

Core tests should pass with this template.

However, the core tests that cover the Composer project templates in core fail when run in this template:

vendor/bin/phpunit web/core/tests/Drupal/BuildTests/Composer/Template/ComposerProjectTemplatesTest.php --filter=testTemplateCreateProject@recommended-project


1) Drupal\BuildTests\Composer\Template\ComposerProjectTemplatesTest::testTemplateCreateProject with data set "recommended-project" ('drupal/recommended-project', 'composer/Template/RecommendedProject', '/web')
COMMAND: COMPOSER_HOME=/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home COMPOSER_ROOT_VERSION=9.3.0 composer create-project --no-ansi drupal/recommended-project testproject 9.3.0 -vvv --repository /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/test_repository/packages.json
OUTPUT:
ERROR: Running 2.1.9 (2021-10-05 09:47:38) with PHP 7.4.2 on Darwin / 18.7.0
Reading ./composer.json (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer.json)
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/config.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Loading config file ./composer.json (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer.json)
Checked CA file /private/etc/ssl/cert.pem: valid
Reading /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/composer.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/config.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/composer.json (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/composer.json)
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Reading /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Creating a "drupal/recommended-project" project at "./testproject"
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/config.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Reading /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/composer.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/config.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/composer.json (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/composer.json)
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Reading /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Reading /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/test_repository/packages.json
Reading file:///Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/test_repository/packages.json
Writing /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/cache/repo/file----Applications-MAMP-tmp-php-build-workspace-78ba9d21989111c8bc37fa31ec93105eMQDn7J-test-repository-packages.json/packages.json into cache
Installing drupal/recommended-project (9.3.0)
Executing command (CWD): rm -rf '/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/testproject'
  - Installing drupal/recommended-project (9.3.0): Symlinking from composer/Template/RecommendedProject
Created project in /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/testproject
Reading ./composer.json (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer/Template/RecommendedProject/composer.json)
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/config.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Loading config file ./composer.json (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer/Template/RecommendedProject/composer.json)
Reading /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/composer.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/config.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/composer.json (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/composer.json)
Loading config file /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Reading /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/auth.json
Loading composer repositories with package information
Reading file:///Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/vendor_packages/packages.json
Writing /Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer-home/cache/repo/file----Applications-MAMP-tmp-php-build-workspace-78ba9d21989111c8bc37fa31ec93105eMQDn7J-vendor-packages-packages.json/packages.json into cache
Executing command (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/core/): git rev-parse HEAD
Executing command (CWD): git rev-parse HEAD
Executing command (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer/Plugin/Scaffold/): git rev-parse HEAD
Executing command (CWD): git rev-parse HEAD
Executing command (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer/Plugin/ProjectMessage/): git rev-parse HEAD
Executing command (CWD): git rev-parse HEAD
Executing command (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer/Plugin/VendorHardening/): git rev-parse HEAD
Executing command (CWD): git rev-parse HEAD
Executing command (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer/Metapackage/PinnedDevDependencies/): git rev-parse HEAD
Executing command (CWD): git rev-parse HEAD
Executing command (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer/Metapackage/CoreRecommended/): git rev-parse HEAD
Executing command (CWD): git rev-parse HEAD
Executing command (/Applications/MAMP/tmp/php/build_workspace_78ba9d21989111c8bc37fa31ec93105eMQDn7J/composer/Metapackage/DevDependencies/): git rev-parse HEAD
Executing command (CWD): git rev-parse HEAD
Updating dependencies
Generating rules
Resolving dependencies through SAT
Looking at all rules.

Dependency resolution completed in 0.001 seconds
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/core-recommended ^9.3 -> satisfiable by drupal/core-recommended[9.3.0].
    - drupal/core-recommended 9.3.0 requires composer/semver 3.2.5 -> found composer/semver[3.2.4] but it does not match the constraint.
  Problem 2
    - Root composer.json requires drupal/core-dev ^9.3 -> satisfiable by drupal/core-dev[9.3.0].
    - drupal/core-dev 9.3.0 requires friends-of-behat/mink-browserkit-driver ^1.4 -> could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.


Failed asserting that 2 matches expected 0.

/Users/joachim/Sites/drupal-core-composer/vendor/phpunit/phpunit/src/Framework/Constraint/Equality/IsEqual.php:96
/Users/joachim/Sites/drupal-core-composer/repos/drupal/core/tests/Drupal/BuildTests/Framework/BuildTestBase.php:300
/Users/joachim/Sites/drupal-core-composer/repos/drupal/core/tests/Drupal/BuildTests/Framework/BuildTestBase.php:287
/Users/joachim/Sites/drupal-core-composer/repos/drupal/core/tests/Drupal/BuildTests/Composer/Template/ComposerProjectTemplatesTest.php:209
/Users/joachim/Sites/drupal-core-composer/vendor/phpunit/phpunit/src/Framework/TestResult.php:722
/Users/joachim/Sites/drupal-core-composer/vendor/phpunit/phpunit/src/Framework/TestSuite.php:677
/Users/joachim/Sites/drupal-core-composer/vendor/phpunit/phpunit/src/Framework/TestSuite.php:677
/Users/joachim/Sites/drupal-core-composer/vendor/phpunit/phpunit/src/TextUI/TestRunner.php:667
/Users/joachim/Sites/drupal-core-composer/vendor/phpunit/phpunit/src/TextUI/Command.php:143
/Users/joachim/Sites/drupal-core-composer/vendor/phpunit/phpunit/src/TextUI/Command.php:96

Error messages when running composer install, after switching from Drupal core 9.2.x to 9.1.x

There is no issue running the steps below when starting a new project with git -

git clone https://git.drupalcode.org/project/drupal.git
cd drupal
composer install
(installs drupal 9.2.x by default)
git checkout 9.1.x
composer install

The steps above, running both composer Install go smooth with no errors.

But when running similar commands using this repo as a base, results in error -
Steps to reproduce:

composer create-project joachim-n/drupal-core-development-project
(will install drupal 9.2.x by default)
cd repos/drupal
git checkout 9.1.x
composer install

error message:

Generating autoload files
Could not scan for classes inside "core/lib/Drupal.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Component/DependencyInjection/Container.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Component/DependencyInjection/PhpArrayContainer.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Component/FileCache/FileCacheFactory.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Component/Utility/Timer.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Component/Utility/Unicode.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Cache/Cache.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Cache/CacheBackendInterface.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Cache/CacheTagsChecksumInterface.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Cache/CacheTagsChecksumTrait.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Cache/CacheTagsInvalidatorInterface.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Cache/DatabaseBackend.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Cache/DatabaseCacheTagsChecksum.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Database/Connection.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Database/Database.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Database/Driver/mysql/Connection.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Database/Driver/pgsql/Connection.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Database/Driver/sqlite/Connection.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Database/Statement.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Database/StatementInterface.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/DependencyInjection/Container.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/DrupalKernel.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/DrupalKernelInterface.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Installer/InstallerRedirectTrait.php" which does not appear to be a file nor a folder
Could not scan for classes inside "core/lib/Drupal/Core/Site/Settings.php" which does not appear to be a file nor a folder
Class Drupal\Core\Composer\Composer is not autoloadable, can not call pre-autoload-dump script


  [RuntimeException]
  Could not scan for classes inside "core/lib/Drupal.php" which does not appear to be a file nor a fold
  er


install [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--dev] [--no-suggest] [--no-dev] [--no-autoloader] [--no-scripts] [--no-progress] [--no-install] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [<packages>]...

Running composer update instead of the last composer install, runs smoothly, no errors.

Add ability to easily check Drupal coding standards

Would you consider it in scope to include drupal-check or similar to allow for easily checking for Drupal coding standards issues when working on core?