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

tabby-output-trail

v0.2.0

Published

Smooth scrolling of terminal output for Tabby: new lines glide into place

Readme

tabby-output-trail

Smooth scrolling of terminal output for Tabby.

When new output pushes the screen up, the content glides into place instead of jumping a whole row at a time. It pairs well with tabby-cursor-trail.

Tested with Tabby 1.0.238 (xterm.js 5.5) on Linux.

Light by design

  • Output is never slowed down. The plugin only observes the terminal; it doesn't touch the data stream. Pushing 100,000 lines takes the same time with and without it (measured in Chromium with xterm.js 5.5: within ±1%, i.e. noise).
  • Almost no CPU. Each write only sets a flag, the real work runs once per animation frame and only while output is arriving, and the glide itself is a CSS transform animated by the browser's compositor (GPU), with no JavaScript per frame. With no output, the plugin does nothing at all.
  • Knows when to stay out of the way. Big chunks of output jump as usual (or, if you prefer, end with a short glide of the last lines), continuous streams (cat, build logs) don't animate at all; full-screen apps (vim, htop, less) and a scrolled-back view are never animated. It also respects the system's "reduce motion" setting.

Install

From Tabby

Settings → Plugins, search for output-trail, click Install, restart Tabby.

Manually

Copy (or symlink) this folder to ~/.config/tabby/plugins/node_modules/tabby-output-trail and restart Tabby. It's plain JavaScript, there is nothing to build.

Settings

Settings → Output trail, with a live preview:

| Option | Default | | |---|---|---| | Enable | on | | | Glide duration | 110 ms | how long new lines take to slide into place | | Maximum lines per glide | 3 | bigger chunks jump instead of gliding | | Big output | Jump | when more lines than that arrive at once: jump as usual, or a short glide of the last lines (everything is already there, only the last few rows slide in) | | Stream filter | 400 ms | output that keeps scrolling longer than this stops gliding until it pauses |

The same options live in Tabby's config.yaml under outputTrail (enabled, duration, maxLines, bigOutput: jump or glide, streamMs).

How it works

A TerminalDecorator attaches to every terminal. After xterm.js parses a write, the plugin schedules one animation frame; in that frame it measures how many lines scrolled and, if it's a small step while you're following the output, animates .xterm-screen from that many rows lower back to its place with the Web Animations API. A new step during a glide continues from the current offset, so consecutive lines stay smooth.

Counting scrolled lines uses baseY plus an xterm.js marker: when the scrollback is full xterm drops the oldest lines and baseY stops growing, but the marker moves up by the number of dropped lines, so the count stays right. It also reads one internal xterm.js field for the cell height (_core._renderService.dimensions), with a fallback, so a major xterm.js upgrade inside Tabby may need a small fix. If something breaks, look for [tabby-output-trail] in the dev tools console (Ctrl+Shift+I).

License

MIT © Paolo Calosso