Dev Dependencies shouldn't count.
So yo, it like this. I'm all like, woah, this Verioneye thing, it will help me keep dependencies up to date and let everyone know my open source project has its shiiiiit together. But then its like, dang it! It makes no distinction for dev dependencies. And since its B-B-B-B-Bower and its not distributed, and dev dependencies don't install with the package; it makes my polished ass project look like fortan. Parse the scopes bro. Make that project shine like it deserves to be.
Comments (8)
-
-
reporter *fist-bump
-
- changed status to resolved
@fresheyeball *fist-bump
Yo bro. Check out your updated project! https://www.versioneye.com/user/projects/5491b268dd709d2cfc0001b1#tab-dependencies
-
reporter Shit dawwwg, its like my repo just got a fresh spray on tan!! Looking golden bra! Thank you, now all the developers will know where to pick up hot upto date code!
-
reporter Homes, let me be real with you. Look at this repo: https://github.com/Fresheyeball/purescript-context . It only has dev scope, but it parses as compile scope! Not cool bro, not cool. Best have some unit tests on that code dawg.
-
@fresheyeball Today is Friday the 13th! I locked out myself from my apartment, had to pay 70 bugs to get in again and by the way the deployment of the background tasks failed! That's why the scope was not parsed correctly on your project. I just restarted the deployment and re parsed your project. Now it works like expected!
https://www.versioneye.com/user/projects/5490a602dd709d3ee2000143#tab-dependencies
I should go to bed and wait until this day is over!
-
reporter Haha. Thanks Robert.
-
@reiz Hey, I am not sure if this works as expected, I just published a public repo on GitHub https://www.versioneye.com/user/projects/5549ca9d5d4f9a44c6001119 which was private (uploaded via API) before https://www.versioneye.com/user/projects/53494695fe0d0720b5000278 . The GitHub version is marked as
out-of-date
and the private one asup-to-date
(which is correct), although the dependencies are the same. The scopes are resolved correctly in both cases, the separate dependencies are shown the same, but the badges are not. - Log in to comment
Makes sense! Should be fixed by end of this week. And your project will shine with a green dependency badge like a Weltmeister project!