fix npm version badge for scoped packages #616
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+1, can we have this merged? |
|
+1 |
|
any word on this? |
|
I'm waiting for this too... |
|
+1 |
|
Sorry for the delay, I'm going through the backlog of issues and PRs… Thanks a lot! It should be live. |
|
@espadrine It is! Thanks! |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support for npm version for scoped packages at
registry.npmjs.org/[package]/latestseems to have been removed. However, you can get the version fromregistry.npmjs.org/-/package/[package]/dist-tags.This pull request partially addresses #429. For full support (download counts) we'll need to wait on npm. Looks like they are working on it though npm/download-counts#23