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

signalk-updater

v1.0.1

Published

Thin-shell SignalK plugin that surfaces the signalk-updater-server console in the admin UI

Readme

signalk-updater

Thin-shell SignalK plugin that opens the SignalK Updater Console from the admin UI and registers the updater engine container for image-update tracking.

The heavy lifting (image listing, version switching, self-update, hardware UI) happens in the signalk-updater-server container, which the signalk-universal-installer drops as a systemd Quadlet. This plugin is just the deep-link from the admin UI.

Status: 0.1.0. First release; pairs with signalk-updater-server 0.x.

What this plugin does

  • Polls for globalThis.__signalk_containerManager (provided by signalk-container).
  • Calls containers.updates.register({...}) to enroll the updater container for update notifications — without ensureRunning. The container's lifecycle is owned by systemd, not this plugin (marine-reliability principle: a broken plugin must never break recovery).
  • Verifies the updater container is running; on any other state, raises a plugin error in the admin UI explaining how to recover (without taking the server down).
  • Serves a webapp at /signalk-updater/ that embeds the Updater Console same-origin under /plugins/signalk-updater/console/. The console proxy forwards to the co-located engine over loopback (http://127.0.0.1:3003); signalk-server runs Network=host so loopback always reaches it with no DNS.

What this plugin does not do

  • Start, stop, or recreate the updater container. The bash installer sets up the systemd Quadlet; this plugin only adopts it for update tracking.
  • Mutate any host state. The managedContainer: true advanced toggle hints at a fallback ensureRunning path, but the default is false and that's what should ship in production.

Configuration

The plugin config schema (src/config/schema.ts) is the source of truth for defaults and constraints; this table is a summary.

| Field | Default | Purpose | | ----------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | managedContainer | false | Advanced opt-in. If true, the plugin attempts to start the container itself instead of relying on the installer's Quadlet. Leave false in production. | | logLevel | info | error | info | debug. | | publishNotifications | true | Republish the updater engine's warn/fail conditions as SignalK notifications. Turn off to keep updater status confined to the Updater Console. | | notificationIntervalSeconds | 60 | How often to poll the engine for status (minimum 10s). Only used when publishNotifications is on. |

Updater notifications

When publishNotifications is on (the default), the plugin polls the engine's GET /api/updater-status and mirrors each warn/fail condition into the SignalK data model under notifications.updater.<id>, so alarm panels (KIP, etc.) surface them:

| Condition (engine status) | Notification state | method | | -------------------------------------------------------------- | -------------------- | ------------------ | | update available on your channel / stale operation lock (warn) | warn | visual | | container stopped/unhealthy / failed self-update (fail) | alarm | visual + sound | | resolved (ok) | cleared → normal | — | | couldn't-measure (unknown) | not raised | — |

Channel-aware update-available: the engine decides "is a newer image available" against the channel you're running — a dirkwa user is warned on a newer dirkwa image (via image-digest drift), a beta user on a newer beta or stable, a stable user only on a newer stable, a master user on a moved master digest. This coexists with (and is more specific than) signalk-container's one-shot notifications.plugins.signalk-updater.updateAvailable.

When a condition recovers, its notification is set to state: normal; the plugin also clears every active notification on stop(), so a shutdown never leaves a stale updater alarm latched. A transient engine-unreachable poll is skipped without clearing existing notifications. The plugin reaches the engine over loopback (http://127.0.0.1:3003 by default; override the port with SIGNALK_UPDATER_ENGINE_PORT). GET /api/updater-status is read-only (token-or-localhost), so the loopback poll needs no token.

Companion repos

| Repo | Role | | ------------------------------------------------------------------------------------ | --------------------------------------------------- | | signalk-universal-installer | Bash bootstrap that drops the systemd Quadlets. | | signalk-updater-server | Engine container — the real updater service. | | signalk-doctor-server | Sister engine container for diagnostics + recovery. | | signalk-container | Cross-plugin container-runtime substrate. |

License

signalk-updater 1.0.0 and later is source available, not open source. See LICENSE.md.

You may, free of charge: run it on your own boat or fleet, private or commercial; use it for internal company operations; modify it for your own use; use it in education and research; and provide professional services around it.

You may not: redistribute it, or publish a modified version of it to npm or anywhere else. Verbatim copies of official releases may be mirrored and cached.

Versions 0.4.0 and earlier remain available under the Apache-2.0 license, see LICENSE-Apache-2.0-through-v0.x.txt.

Contributing

See CONTRIBUTING.md.