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.
One of the bits of info we collected from library authors was NPM info so that we could do things like automatically create a CDN script tag, fetch the license if not manually provided, and show users how actively developed the library is. This does some of that initial fetching, currently in a quick-and-dirty little list of tags:
@Qianqianye This additional info isn't currently in the designs because we were considering it a nice-to-have that we might not have had the ability to collect, but it looks like it's going to be feasible. Design-wise, what do you think the best approach for something like this should be? One option is to try to mimic the style of tags the designers had in some old iterations for things like examples, which we later took out from that section. Another option is to just hide this info for now and think of a more permanent placement at a later date.