-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Badge request: GitHub NPM package.json - optionalDependencies #6044
Labels
Comments
5 tasks
Just to clarify the request here, at the moment the "GitHub package.json dependency version" badge can optionally accept a
|
paulmelnikow
added a commit
that referenced
this issue
Jul 9, 2021
If this issue is unresolved, I would like to work on this issue. |
@Nazeeh21 - go for it 👍 |
I thought this was sorted by #6749 (pending merge)? |
Oh yes so it is - scratch that! |
calebcartwright
pushed a commit
that referenced
this issue
Aug 3, 2021
Closes #6044 Co-authored-by: repo-ranger[bot] <39074581+repo-ranger[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
📋 -
optionalDependencies
from NPM package.json at GitHub need be supported like it supporteddependencies
anddevDependencies
.Example of view:
dependencyName: version
.🔗 - similar to the getting of GitHub package.json
devDependencies
anddependencies
🎤 - by default badges demonstrates packages that required to use, but optionalDependencies will provide info to user about packages that used, but can be substituted without damage to package
The text was updated successfully, but these errors were encountered: