Skip to content
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

flow-typed usage metrics #4113

Open
Brianzchen opened this issue Jul 25, 2021 · 0 comments
Open

flow-typed usage metrics #4113

Brianzchen opened this issue Jul 25, 2021 · 0 comments

Comments

@Brianzchen
Copy link
Member

Brianzchen commented Jul 25, 2021

Do you want to request a feature or report a bug?
feature

What is the current behavior?
N/A

If this is a feature request, what is motivation or use case for changing the behavior?
Albeit less than TS, we do have many flow-typed defs. It would be interesting if there was a metric of usage to better understand, which defs the community largely depended on and need maintenance vs completely unused which gives the chance to clean up, eg: styled-components in their earlier iterations have completely broken tests that would need a major overhaul but we don't know what the impact would be.

I'm also interested to know how many consumers there are vs the handful of contributors.

Metrics could include

  • Downloads, which can be pinged everytime flow-typed install is run on a single dependency regardless if an update actually happens to the users codebase
  • flow-typed install of non-existent defs which would cause stubs which can help to understand defs that may be missing
  • reports split up by flow version to form a metric on what version the community is largely on
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant