-
-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packagist fallback for Composer #52
Comments
Would you like to submit a PR for that? It's should be pretty simple like the npm implemention https://github.com/github-linker/live-resolver/blob/3220ddfd55a0a86ae08dc95ed9e7b823f9d8d240/src/resolver/npm.js#L20-L22 |
stefanbuck
added a commit
to OctoLinker/api
that referenced
this issue
Oct 28, 2015
Implemented see OctoLinker/api#4 |
josephfrazier
added a commit
to josephfrazier/browser-extension
that referenced
this issue
Jan 15, 2018
…ctoLinker#52) * npm: Guess that the repo might be $maintainerUsername/$packageName This can help in cases where the repo exists, but isn't referenced in package.json. See here for more information about the npm registry API response fields: https://github.com/npm/registry/blob/51b9a9467a63cc4a4929590a7044e2612377c102/docs/responses/package-metadata.md * npm: Test case where repo exists, but isn't in package.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the composer lookup fails, you could use the Packagist link instead:
https://packagist.org/packages/{vendor}/{client}
eg. https://packagist.org/packages/google/apiclient
The text was updated successfully, but these errors were encountered: