npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

spotify-review

v1.2.0

Published

Analyze your Spotify listening data

Downloads

15

Readme

spotify-review

Analyze your Spotify listening data

Installation

npm install -g spotify-review

Usage

Setup your database:

spotify-review init /path/to/EndSong.json

Once your database is set up you can perform individual queries or generate a full report:

spotify-review report
spotify-review analyze topSongs

To view available analysis commands use:

spotify-review analyze --help

Notes

  • Q: Why is the minutes listened calculation so much higher than what I see in Spotify Wrapped?

    A: I'm not really sure. Ultimately I don't know what Spotify counts as "listening time" in their calculation. For a given year, spotify-review uses the sum of ms_played (converted to minutes) for any entry with a track_name field and ts in that year.

    I've tried many other criteria for what "listening time" is, including:

    • filtering tracks that stopped due to errors
    • requiring a minimum amount of time listened (10s, 20s, 30s etc)
    • selecting entries from the previous year's Spotify Wrapped date until the current year's date
    • selecting entries between Jan 1 and Oct 31
    • many more

    Selecting entries between Jan 1 and Oct 31 gets pretty close usually but it's never exact, so I don't think that's correct. The "listening time" calculation also seems to affect the Top (Songs/Albums/Artists) calculations, since those don't quite align with what Spotify provides either (although they are very close). If you have any ideas open an issue/PR.