Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
ComposerRepository::getProviderNames has different behavior in case providers are provided as partial packages #8526
I am actually migrating some projects using private packages to laminas.
In laminas/laminas-dependency-plugin#6 I've reported a bug, that our projects do not properly migrate due to the
After some debugging with composer, I found out, that the provider names are not properly returned for lazy packages. Private packagist creates a
I've created a possible fix in #8516
Would love to get any feedback in the PR.
Do you have the laminas packages present in your private packagist instance or not? If yes I assume the plugin should work correctly, but I am not 100% sure I understand the implications of the hackery they are doing here tbh.
In any case your patch seems harmless enough that I am fine merging it, but I don't really understand why it fixes things, nor what the problem is exactly that you experienced.
Yes, they are present in my private packagist.
Probably some legacy stuff? I found a work around without creating a new assumption of having "packages" available in the package.json