-
Notifications
You must be signed in to change notification settings - Fork 56
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
A way to sanitize spiked/flooded download data #173
Comments
note that a similar spike happened to vue, so you're either looking at manually patching historical data on a package name + timeframe basis which is an ongoing effort, or you'd need to apply some kind of heuristic to find unrealistic spikes and flatten them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Svelte package recently had their download numbers flooded with a huge amount of downloads for a short amount of time. This makes the graph unreadable as the downloads spike compresses the graph all the way down.
https://npmtrends.com/svelte
I am searching for a way to clean up this spike, so I can actually view the unsquashed graph.
I did make this super hacky workaround to flatten the date, if you're really desperate to see the realistic graph:
In the .js bundle on the npmtrends site I found the success handler for fetch requests. It looks like this:
I put a breakpoint of the
setData
line and executed this in the terminal when the t value is the graph data:You can trigger the downloads data fetch by selecting a new time interval in the dropdown on the page.
The text was updated successfully, but these errors were encountered: