Using a composer (proxy) repository in SonaType's Nexus with other repositories than packagist.org.
How could we solve this issue? (Not knowing is okay!)
Instead of a lookup via the entries of the list key, invoke a HEAD request with the well-formated vendor and package name according to the format string under providers-url etc.. Not sure though.
What are you trying to do?
I want to proxy the Asset Packagist composer repository, which does not provide the
list
key in itspackage.json
under https://asset-packagist.org/packages.json. And according to thecomposer-repository
JSON scheme it's not a required key. See oneOf section in composer-repository-schema.json.Besides, our company private registry based on satis, also does not contain the
list
key:or when
providers
is set totrue
insatis.json
:What feature or behavior is this required for?
Using a composer (proxy) repository in SonaType's Nexus with other repositories than packagist.org.
How could we solve this issue? (Not knowing is okay!)
Instead of a lookup via the entries of the
list
key, invoke a HEAD request with the well-formated vendor and package name according to the format string underproviders-url
etc.. Not sure though.