Closed jmonkfish closed 1 year ago
Sounds reasonable. Can you please make PR?
Okay, working on the documetation.
Should we file a separate issue for the "Ready to use!" being displayed even for packages which are not usable (npm-asset/pngquant-bin)?
Umm... I thought the package is not generally unusable and cannot be used with some other packages.
Now I've tried and I see that the package npm-asset/pngquant-bin
is completely uninstallable.
So. We can point it in documentation. And basically that's all that can be done for now.
When an npm package has dependency conflicts with min/max version requirements (such as with npm-asset/pngquant-bin), composer is not able to resolve the problem. npm is able to resolve the issue during install, and asset-packagist.org marks the package as "Ready to use!"
This is not documented with asset-packagist except within a few closed issues. It would likely benefit others looking to use asset-packagist.org to know that currently composer is not able to resolve dependency version conflicts for npm packages.