Generate archive of historical analysis data #62
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a package
@arethetypeswrong/history
, generated by a script that runs the core analysis on each package in npm-high-impact at different points in time. (Specifically, it generates analysis for the latest version of each package for its latest version available on the first of every month since January 2022.--moduleResolution nodenext
was first released to stable versions of TypeScript in May of 2022, so there’s no need to go further back than this.) The result is a large archive of data that can be used to analyze how TS-compatible the most important npm packages are, and how that’s changing over time.The generated analysis is saved as a 1.2 GB newline-delimited JSON file, cached in Azure Storage for incremental updates going forward, and compressed down to an incredible 34 MB to be shipped in the npm package. A small JavaScript interface decompresses the file and provides access to a POJO. I anticipate including smaller bundleable reduced datasets in the future, perhaps to allow trends in the data to be explored via web UI.