search

tc39 / proposal-uuid

UUID proposal for ECMAScript (Stage 1)
463 stars 7 forks source link

Update usage statistics #39

Open dead-claudia opened 3 years ago

dead-claudia commented 3 years ago

Sources:

Yes, you're reading those increases correctly. It's almost tripled in usage since June 2019 (1.7-1.8x increase for both).

I used October for my reference point as November obviously has not completed yet (though at the time of writing there's been about 122M downloads this month) and that data source does not include a "last month" measure, only aggregate per day/week/month/year.

dead-claudia commented 3 years ago

For context, those download counts exceed lodash and the dependent repo counts are about 80% of that module's as well.

ctavan commented 3 years ago

Thank you for the update @isiahmeadows. Would you mind running prettier to satisfy the Travis checks?

broofa commented 3 years ago

Anyone know what might be driving the increase in downloads? At first glance this does appear to be something specific to this module. E.g. uuid #'s are up ~100% since the beginning of the year vs. lodash up ~50%, or request (not actively developed) is up ~25%.

My guess would be an increase in adoption of one or more dependent modules, but seeing as uuid is in the top 20, I'm skeptical that it's just one module. It'd have to be something in the top 50-100 (maybe???) to move the needle that much. I'm not aware of anything like that (but haven't been looking for it so maybe just me?).

Otherwise some sort of broader industry trend, perhaps? E.g. Improved support for UUIDs as primary keys in DBs? Adoption of UUIDs as the default identifier on app development platforms?

Curious.

bcoe commented 3 years ago

@isiahmeadows looks like you just need to run fix from the CLI, for the benefit of the linter.

dead-claudia commented 3 years ago

Sorry for the long delay (IRL concerns), but updated.

dead-claudia commented 3 years ago

BTW, I ran Prettier, and got no issues, so I don't know what Travis is doing here. Edit: figured it out. Forgot to include the changes in my commit, which is now fixed.