-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add dependencies from package.json to Packages table in README.md #1161
Conversation
This is rad @jonahweissman, thank so much for completing the table! The appveyor badges are indeed more tricky, you should be able to get them using Do you feel like still doing that part? |
@diasdavid Yeah, no problem! I'll get it done soon |
@diasdavid I have added the AppVeyor badges! Unfortunately, I couldn't figure out how to find the link the AppVeyor project, so I just made them images. I'm guessing someone with write access needs to do that because AppVeyor was giving me
when I tried to go to the project pages. (Example of page that I can't view: https://ci.appveyor.com/project/wubalubadubdub/ipfs-repo) Also, some of the coverage badges show up as "unknown" and the project pages say
I tried to "add repo" on Coveralls, but, again, I think someone with write access needs to that. |
This is great @jonahweissman 🌟 Now we have a way to tell which repos are missing and what. |
This switches out `tar-stream` for [`it-tar`](https://www.npmjs.com/package/it-tar), which is a fork that uses pure async iterables. This removes `readable-stream` from this branch of the tree (which will allow us to drop it entirely in the future) and allows us to drop the `event-iterator` dependency.
I checked the
README.md
for each repo to find the missing badges. A lot were missing Circle CI and coverage badges. I couldn't find the AppVeyor badges for any of them, but I probably just don't know where to look. If someone tells me how, I'd be happy to add the missing badges.Here are the packages I added. I may have missed some.
closes #1050