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

zosenlink-node-client

v1.0.3

Published

Node.js wrapper for the ZosenLink managed frpc client.

Readme

ZosenLink Node Client

zosenlink-node-client is a minimal managed frpc wrapper for Node.js hosts. It accepts exactly one positional argument: the activation key.

./zosenlink-node-client <activation-key>

The platform URL is fixed to https://zosen.link. Runtime status events are emitted to stdout as JSON Lines, one object per line, so Node.js can listen to child.stdout.

Example:

import { spawn } from "node:child_process";

const child = spawn("./zosenlink-node-client", ["dev-activation-key"]);

child.stdout.on("data", (chunk) => {
  for (const line of chunk.toString().trim().split("\n")) {
    if (!line) continue;
    console.log(JSON.parse(line));
  }
});

child.stderr.on("data", (chunk) => {
  console.error(chunk.toString());
});

NPM wrapper example:

const { startZosenLinkClient } = require("zosenlink-node-client");

const child = startZosenLinkClient("dev-activation-key", {
  onEvent(event) {
    console.log(event);
  }
});

child.stderr.on("data", (chunk) => {
  process.stderr.write(chunk);
});

The npm package expects platform binaries under:

bin/
  darwin-arm64/zosenlink-node-client
  darwin-x64/zosenlink-node-client
  linux-x64/zosenlink-node-client
  win32-x64/zosenlink-node-client.exe

Build examples:

cd apps/zosenlink-node-client
GOOS=darwin GOARCH=arm64 CGO_ENABLED=0 go build -trimpath -ldflags='-s -w' -o bin/darwin-arm64/zosenlink-node-client .
GOOS=darwin GOARCH=amd64 CGO_ENABLED=0 go build -trimpath -ldflags='-s -w' -o bin/darwin-x64/zosenlink-node-client .
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -trimpath -ldflags='-s -w' -o bin/linux-x64/zosenlink-node-client .
GOOS=windows GOARCH=amd64 CGO_ENABLED=0 go build -trimpath -ldflags='-s -w' -o bin/win32-x64/zosenlink-node-client.exe .

# Optional artifact build path used by the repo:
go build -trimpath -ldflags='-s -w' -o ../../artifacts/zosenlink-node-client-darwin-arm64/zosenlink-node-client .
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -trimpath -ldflags='-s -w' -o ../../artifacts/zosenlink-node-client-linux-amd64/zosenlink-node-client .
GOOS=windows GOARCH=amd64 CGO_ENABLED=0 go build -trimpath -ldflags='-s -w' -o ../../artifacts/zosenlink-node-client-win64/zosenlink-node-client.exe .