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 🙏

© 2026 – Pkg Stats / Ryan Hefner

yet-another-pomodoro

v0.0.3

Published

yet another pomodoro app

Downloads

17

Readme

Yet Another Pomodoro

installation

npm i -g yet-another-pomodoro

usage

TODO

Mission statement (initial commit)

Problem to solve:

A productivity pomodoro application that will block messenger apps on MY setup.

Specifically in my case it's enough to block access to one workspace (nr 2) on my i3 setup.

So, an application should allow this:

  • a settings file (sensible default would be ~/.tarnas-pomodoro)
  • a persistence file (sensible default would be ~/.tarnas-pomodoro.storage)
  • standard options to manage productivity time, short and long breaks (default 25/5/15)
  • start pomodoro
  • stop pomodoro
  • next period
  • ask for current state (whether we are in pomodoro or not, what type of period we are in, how long till end)

the last affordance is the most critical one!

output should be plaintext, that could be easily managed by bash scripts

why:

  • it will be used to write a polybar script that will be polling for the pomodoro state every N seconds
  • it will be used to decide if the user should be allowed to run a specific shell command e.g. tarnas-pomodoro state | not-in-pomodoro && i3-msg workspace 2

in the pseudo-snippet above, not-in-pomodoro is the simplest possible check we can find to decide if the next command should be executed

so if the output is POMODORO 18:13 or SHORT-BREAK 4:23 or LONG-BREAK 11:22 you can have

[[ $(tarnas-pomodoro state) != POMODORO* ]] && i3-msg workspace 2

^ the above will probably be the interface we go with

very optionally

some history for statistics or some shit