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 🙏

© 2025 – Pkg Stats / Ryan Hefner

signalk-logviewer

v0.3.1

Published

SignalK Plugin to view and filter server logs

Readme

Signal K Log Viewer

The motivation for this simple Webapp log viewer is that Sever -> Server Log is often cluttered and not searchable. Acts like "tail -n xxxx" and you can "grep" in the output. Victron VenusOS see below.

Requirements

  • SignalK 2.15 or higher
  • Systemd logging or Victron Cerbo GX (tested v3.66 and v3.70-beta)

Features

  • Get up to 50000 last lines from log, 2000 lines by default
  • Filter log
  • Copy to clipboard
  • Timestamp format options:
    • Original: Shows timestamps as they appear in the log file (default for TAI64N on Cerbo)
    • ISO 8601: Converts TAI64N timestamps to ISO 8601 format (e.g., 2025-01-15T10:30:45.123Z)
    • Locale: Converts timestamps to your browser's local time format
  • Cerbo GX permission warning: Automatic detection and guidance for Venus OS users

Victron Venus OS (Cerbo GX / Octo GX / Venus GX)

  • Issue #1 The log directory /data/log/signalk-server is owned by root:root, but the plugin runs as signalk:signalk, so it needs permission to access the log files.
  • Issue #2 Also the 25kb limit for the log file are way too small.
  • The following has been successfully tested on VenusOS 3.66:

Quick Fix (temporary - resets on reboot)

  1. SSH into your device as root
  2. Execute:
chown -R signalk:signalk /data/log/signalk-server

Persistent Solution (survives reboot)

  1. SSH into your device as root
  2. Create /data/rc.local file:
cat > /data/rc.local << 'EOF'
#!/bin/sh
# Fix SignalK log permissions
chown -R signalk:signalk /data/log/signalk-server
EOF
  1. Make it executable:
chmod +x /data/rc.local
  1. Reboot your device:
reboot

Increase LOG size, default is only 25kb

  1. SSH into your device as root
  2. Backup original file
cp /opt/victronenergy/service/signalk-server/log/run /data/run.backup
  1. Edit /opt/victronenergy/service/signalk-server/log/run file:
cat > /opt/victronenergy/service/signalk-server/log/run << 'EOF'
#!/bin/sh
exec 2>&1
exec multilog t s2500000 n4 /var/log/signalk-server
EOF
  1. Reboot your device:
reboot

Note: The plugin automatically detects Venus OS devices (Cerbo GX, Octo GX, Venus GX) and displays an error message with these instructions if logs cannot be accessed.

Changelog

Changelog at Github master

Bug reports

GitHub Issues

Contributing

Contributions are welcome! Please:

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests if applicable
  5. Submit a pull request

License MIT