Installing starterkit via composer 2 leads to lots of psr-4 related errors

Hi, I’m on Mac Big Sur latest, using Composer version 2.0.9 2021-01-27 16:09:27 installed via brew, I’m trying to install the starterkit. Using this:

composer create-project getkirby/starterkit esolia-kirby

It starts off looking good, then when it starts installing plugins, it goes south quickly, leading to a lot of psr-4 related errors and skipping, e.g.:

Class Kirby\Database\Sql located in ./kirby/src/src/Database/Sql.php does not comply with psr-4 autoloading standard. Skipping.

Pasted the whole log from std-out in this gist:

I found a statement somewhere saying that it has to do with the autoloader section of the composer.json, but, there’s no such section in this case.

Can anyone say what I need to do to get it to install correctly? I’m afraid I’m utterly new to composer…

Yes, I get the same messages but it doesn’t seem to affect functionality at all.

Ping @lukasbestle

Thanks for the quick answer. Glad to hear it’s cosmetic!

I had the same output lately and couldn’t track down why it happened.

Unfortunately I cannot reproduce this again. I just tested it with the same Composer version and got the following output:

Creating a "getkirby/starterkit" project at "./starterkit"
Installing getkirby/starterkit (3.5.1)
  - Installing getkirby/starterkit (3.5.1): Extracting archive
Created project in /Users/lux/Desktop/starterkit
Loading composer repositories with package information
Updating dependencies
Lock file operations: 13 installs, 0 updates, 0 removals
  - Locking claviska/simpleimage (3.5.1)
  - Locking filp/whoops (2.9.1)
  - Locking getkirby/cms (3.5.1)
  - Locking getkirby/composer-installer (1.2.1)
  - Locking laminas/laminas-escaper (2.7.0)
  - Locking laminas/laminas-zendframework-bridge (1.1.1)
  - Locking league/color-extractor (0.3.2)
  - Locking michelf/php-smartypants (1.8.1)
  - Locking mustangostang/spyc (0.6.3)
  - Locking phpmailer/phpmailer (v6.2.0)
  - Locking psr/log (1.1.3)
  - Locking symfony/polyfill-mbstring (v1.22.0)
  - Locking true/punycode (v2.1.1)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 13 installs, 0 updates, 0 removals
  - Installing getkirby/composer-installer (1.2.1): Extracting archive
  - Installing symfony/polyfill-mbstring (v1.22.0): Extracting archive
  - Installing true/punycode (v2.1.1): Extracting archive
  - Installing phpmailer/phpmailer (v6.2.0): Extracting archive
  - Installing mustangostang/spyc (0.6.3): Extracting archive
  - Installing michelf/php-smartypants (1.8.1): Extracting archive
  - Installing laminas/laminas-zendframework-bridge (1.1.1): Extracting archive
  - Installing laminas/laminas-escaper (2.7.0): Extracting archive
  - Installing psr/log (1.1.3): Extracting archive
  - Installing filp/whoops (2.9.1): Extracting archive
  - Installing league/color-extractor (0.3.2): Extracting archive
  - Installing claviska/simpleimage (3.5.1): Extracting archive
  - Installing getkirby/cms (3.5.1): Extracting archive
5 package suggestions were added by new dependencies, use `composer suggest` to see details.
Generating optimized autoload files
7 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

:man_shrugging:

Yes, I get the same messages but it doesn’t seem to affect functionality at all.

Shouldn’t the claim be no warning even with the current version of Composer?
Composer 2 will not change the behaviour. It is even mentioned here: Composer 2.0 is now available!

Invalid PSR-0 / PSR-4 configurations will not autoload anymore

I also tested it again, and now I don’t get the error messages anymore.