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-plugin-sync

v0.1.1

Published

Keep your installed Tabby plugins in sync across machines through config.yaml

Readme

tabby-plugin-sync

Keep the installed Tabby plugins the same on every machine.

Tabby can sync config.yaml — with its built-in Config sync, or with any file sync tool (Syncthing, Koofr, Dropbox, Nextcloud…) — but the plugins you install live in the plugins folder and aren't recorded anywhere, so every new machine starts without them. This plugin writes the list of installed plugins into config.yaml, and on each machine:

  • installs the plugins that are missing
  • updates plugins that are newer elsewhere
  • removes plugins you uninstalled on another machine (optional)
  • adds plugins you install here to the shared list

When it changes something it asks you to restart Tabby, since plugins load at startup.

Install

Install it on every machine (this one plugin can't install itself): Settings → Plugins, search for plugin-sync, click Install, restart Tabby. Make sure config.yaml is synced between the machines, through Settings → Config sync or your file sync tool.

On the first machine, the plugin records what you have installed. On the others, it installs whatever is missing, and adds what they had that the first machine didn't. No plugins are removed on a machine's first sync.

Settings

Settings → Plugin sync shows every plugin with its version in the shared list and on this machine, and what will happen to it. From there you can:

  • turn the sync on or off
  • choose whether plugins uninstalled elsewhere are removed here
  • untick a plugin to stop syncing it on this machine only
  • run a sync now and restart Tabby
  • see the machines that share the list, and forget old ones

Using a file sync tool

Tabby reads config.yaml only at startup and rewrites the whole file every time it saves a setting. With a file sync tool that means changes coming from another machine are ignored while Tabby runs, and then overwritten by the next save.

With Reload config.yaml when it changes on disk turned on (the default), this plugin watches the file and reloads Tabby's config when it changes, so those changes are picked up live and no longer get lost. It also re-reads the file before every sync. If config.yaml is a symlink into a synced dotfiles folder, the plugin watches the real file. Encrypted configs are never reloaded automatically, since that would ask for the password each time.

How it works

The shared list lives in config.yaml under pluginSync.plugins, with each machine's last known state under pluginSync.machines. A sync is a three-way merge between the shared list, the plugins installed here, and what this machine had after its previous sync. That last part is what tells the two cases apart: a plugin that is missing here because you uninstalled it here (drop it from the list), or because it was installed elsewhere (install it here).

Each Tabby installation gets an id, kept in plugins/plugin-sync-machine.json. A fresh Tabby install with an empty plugins folder is treated as a new machine, so it gets everything installed instead of wiping the list for everyone.

Plugins symlinked into the plugins folder for development are never upgraded or removed, and the plugin never removes itself.

Installs go through Tabby's own plugin manager, so the same rules apply: only tabby-* and terminus-* packages from npm, with the versions in the list.

License

MIT © Paolo Calosso