I'm asking because I'm running into multiple variations of this error when I try running `composer update` or `composer require any/package`:

found another/package[0.0.1] in the lock file but not in remote repositories

All the packages that show that error are in the "path" repository and also in the lock file, and I can't figure out how to resolve this error so that I can require additional (external) packages.

#PHP #Composer

Fireside Fedi Episode 28 starts NOW! With me today is @opensourcegaming Franzo! Franzo is an #Italian #FOSS #Software #Games Lover, #Composer, #developer. Franzo #streams on #Peertube and #uploads all #music and shows to it as well.

Watch the show live:
#Owncast #Livestream - https://stream.firesidefedi.live

After the show:
#Peertube #VOD - https://video.firesidefedi.live
#Castopod #Fedicast - https://audio.firesidefedi.live
#Youtube - https://www.youtube.com/channel/UCaJ15PXgRihoPku7JMdDnsw

All #Links - https://firesidefedi.live

#stream #owncast #live #interview #firesideFedi #FsF #people #peopleOverPlatforms #protocolsOverPlatforms #fedi #fediverse #open #internet #openInternet #podcast #fedicast #livestream #show #episode #peertube #vod #castopod #writefreely #lemmy #boostplease #fedizen #btfree #bigTechFree #nonprofit #signup #tubeFree

If you're enjoying the show, please consider supporting our new nonprofit btfree.org at https://givebutter.com/btfree. We're currently running https://tubefree.org which is a moderated peertube open for signups right now!

When specifying a "path" repository with a wildcard, does Composer do a recursive scan of the subdirectories for packages (i.e., composer.json files)?

I'm asking about when you have configuration like this:

{
"repositories": {
"modules": {
"type": "path",
"url": "modules/*"
}
}
}

#PHP#Composer