Shields: npm dev dependency version badge not working with scoped dependencies
Are you experiencing an issue with...
- [x] [shields.io](https://shields.io/#/)
- [ ] My own instance
- [ ] [gh-badges NPM package](https://www.npmjs.com/package/gh-badges)
use:
/npm/dependency-version/react-boxplot/dev/@babel/core
https://img.shields.io/npm/dependency-version/react-boxplot/dev/@babel/core.svg
expected:
@babel/core ^7.0.0
result:
404 badge not found
kimseongrim
All 4 comments
The reason this isn't working is because you're missing the user/org of the repo.
I think you're trying to do this:
- 
chris48s
on 6 Apr 2019
The modal window in the UI still looks buggy to me, as it's missing the field for the username:
calebcartwright
on 6 Apr 2019
@chris48s - I still think this is a bug with npm badge. If I'm wrong or missing something please let me know though.
The npm dependency version and github package.json version badges are different and while the package.json version badge can indeed be used as workaround, I think the route pattern for the npm dependency version badges can't handle scoped dependencies due to the extra / scope deps add.
calebcartwright
on 6 Apr 2019
Oh yes. You're right - sorry. I hadn't noticed that we have 2 slightly different approaches to npm dependency-version
chris48s
on 6 Apr 2019
Related issues
rominf
路
3Comments
korenyoni
路
3Comments
Turnerj
路
3Comments
Fazendaaa
路
3Comments
kirankotari
路
3Comments
Most helpful comment
@chris48s - I still think this is a bug with npm badge. If I'm wrong or missing something please let me know though.
The npm dependency version and github package.json version badges are different and while the package.json version badge can indeed be used as workaround, I think the route pattern for the npm dependency version badges can't handle scoped dependencies due to the extra
/scope deps add.