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

@rljson/network

v0.0.15

Published

Networking middle layer providing basic advertising and discovery as well as cloud fall backs and basic config.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

inlavigoinlavigogabriel.gatzschegabriel.gatzschejan-balzerjan-balzerheller64heller64

Keywords

Readme

Trouble shooting

Table of contents

Hub election looks correct but clients stay on old hub

Date: 2026-03-20

Problem:

NetworkManager correctly emits hub-changed when the elected hub changes, but clients in @rljson/server stayed connected to the old hub, causing split-brain.

Root Cause:

This was NOT a bug in @rljson/network. The hub-changed event was emitted correctly. The problem was in @rljson/server's Node class which only listened to role-changed and ignored hub-changed.

Fix:

@rljson/[email protected] — Node now subscribes to both role-changed and hub-changed events.

Lesson:

When debugging topology issues, check both the emitter (NetworkManager) and the consumer (Node). The event was correct — the listener was missing.

Vscode Windows: Debugging is not working

Date: 2025-03-08

⚠️ IMPORTANT: On Windows, please check out the repo on drive C. There is a bug in the VS Code Vitest extension (v1.14.4), which prevents test debugging from working: https://github.com/vitest-dev/vscode/issues/548 Please check from time to time if the issue has been fixed and remove this note once it is resolved.