4 ms·

Does this include typescript projects? i couldn't find my own.[0] Also, I can see my two most popular packages ( 40 stars[1] and 14[2] respectively), and I've

by ldd 6y ago

Does this include typescript projects? i couldn't find my own.[0] Also, I can see my two most popular packages ( 40 stars[1] and 14[2] respectively), and I've realized that not updating them frequently probably hurts. The thing is, what about bots like dependabot? I have one or two other packages that auto update and close issues quickly because they have some bots helping out, and I was wondering if you took that into account. I am also sad that things that I worry about, like testing, and bundle size are nowhere to be found. But overall, great idea. Keep at it! [0]:https://github.com/ldd/vscode-jq/ https://github.com/ldd/vscode-jq/ [1]:https://openbase.io/js/gatsby-source-github-api https://openbase.io/js/gatsby-source-github-api [2]:https://openbase.io/js/react-tech-tree https://openbase.io/js/react-tech-tree

liorgrossman 6y ago
Thanks! We currently only cover npm packages (not all GitHub repos), does vscode-jq have an npm package? We currently don't have any special handling for bots, but this is on the pipeline. Same goes for consolidating contributors (sometimes the same person shows up as 2 different GitHub users, you can see that on GitHub too). Bundle size is a big one for us, highly prioritized. Testing isn't, though, what would you like to see about testing that isn't covered by badges? (e.g. test coverage, passing/failing, etc.)
- ldd 6y ago
  aha! covering npm packages makes sense. I briefly forgot that I hadn't publish that one on npm. I wonder if vscode extensions are published on npm... umm... I'm glad you have all those future features planned. As for testing, I think that badges are often times not enough. I'd like to see if tests exist at all in the first place, and the quality or helpfulness of those tests. But maybe I'm in the minority for that, so ask other users for confirmation. :D
  - liorgrossman 6y ago
    Hehe :) A few other people asked about testing, too, but it's going to be challenging to build something that works reliably at scale with different codebases and testing frameworks. But I think I got the idea of what you're looking for now. This will help us better model this feature if we end up implementing it. Thanks for the feedback!

by ldd 6y ago

liorgrossman 6y ago

Thanks! We currently only cover npm packages (not all GitHub repos), does vscode-jq have an npm package? We currently don't have any special handling for bots, but this is on the pipeline. Same goes for consolidating contributors (sometimes the same person shows up as 2 different GitHub users, you can see that on GitHub too). Bundle size is a big one for us, highly prioritized. Testing isn't, though, what would you like to see about testing that isn't covered by badges? (e.g. test coverage, passing/failing, etc.)

ldd 6y ago
aha! covering npm packages makes sense. I briefly forgot that I hadn't publish that one on npm. I wonder if vscode extensions are published on npm... umm... I'm glad you have all those future features planned. As for testing, I think that badges are often times not enough. I'd like to see if tests exist at all in the first place, and the quality or helpfulness of those tests. But maybe I'm in the minority for that, so ask other users for confirmation. :D
- liorgrossman 6y ago
  Hehe :) A few other people asked about testing, too, but it's going to be challenging to build something that works reliably at scale with different codebases and testing frameworks. But I think I got the idea of what you're looking for now. This will help us better model this feature if we end up implementing it. Thanks for the feedback!