Discussion · Bonfire social

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

Michael T

@mitelg@phpc.social · 15 hours ago

@ramsey yes, it does. we are using this in #shopware https://github.com/shopware/shopware/blob/trunk/composer.json#L218

Ben Ramsey

@ramsey@phpc.social · 16 hours ago

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

dpi

@dpi@phpc.social · 5 hours ago

@ramsey found that using this repo method, setting a `version` key in the composer.json files of the fake projects you’re including is a quick solve for resolution pain points. I know they there’s root version env var and maybe other things also…

Bonfire social

This is a bonfire demo instance for testing purposes

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.0-rc.1.30 no JS en

Automatic federation enabled