Magento 2.4.7 composer throws exception after module removal with static content

Question

Need a hint here.

I just removed a module and cleared static content. Now when I try to use composer (i.e. bin/magento setup:di:compile or any other command involving bin/magento I get this:

There is an error in /var/www/website.com/vendor/composer/composer/src/Composer/IO/BaseIO.php at line: 95
Composer\IO\BaseIO::checkAndSetAuthentication(): Argument #2 ($username) must be of type string, null given, called in /var/www/website.com/vendor/composer/composer/src/Composer/IO/BaseIO.php on line 168#0 /var/www/website.com/vendor/composer/composer/src/Composer/IO/BaseIO.php(168): Composer\IO\BaseIO->checkAndSetAuthentication()
#1 /var/www/website.com/vendor/composer/composer/src/Composer/Factory.php(357): Composer\IO\BaseIO->loadConfiguration()
#2 /var/www/website.com/vendor/composer/composer/src/Composer/Factory.php(634): Composer\Factory->createComposer()
#3 /var/www/website.com/vendor/magento/framework/Composer/ComposerFactory.php(47): Composer\Factory::create()
#4 /var/www/website.com/vendor/magento/framework/Composer/ComposerInformation.php(368): Magento\Framework\Composer\ComposerFactory->create()
#5 /var/www/website.com/vendor/magento/framework/Composer/ComposerInformation.php(381): Magento\Framework\Composer\ComposerInformation->getComposer()
#6 /var/www/website.com/vendor/magento/framework/Composer/ComposerInformation.php(244): Magento\Framework\Composer\ComposerInformation->getLocker()
#7 /var/www/website.com/vendor/magento/framework/App/ProductMetadata.php(120): Magento\Framework\Composer\ComposerInformation->getSystemPackages()
#8 /var/www/website.com/vendor/magento/framework/App/ProductMetadata.php(80): Magento\Framework\App\ProductMetadata->getSystemPackageVersion()
#9 /var/www/website.com/vendor/magento/framework/Console/Cli.php(101): Magento\Framework\App\ProductMetadata->getVersion()
#10 /var/www/website.com/bin/magento(22): Magento\Framework\Console\Cli->__construct()
#11 {main}

• joesk: Depends on where you are doing this but it could easily be the opcache needs to be cleared first.
• jean-gabriel cabanas: I checked, it's not opcache related :/
• jean-gabriel cabanas: I reloaded a backup from an hour before, and now everything is fine...so. Let's close this.