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

@moecorp/moelog-sidecar

v0.0.2-alpha.1

Published

El canal sidecar de MoeLog: protocolo, transporte, daemon y CLI. Compartido por todos los SDK de servidor.

Readme

@moecorp/moelog-sidecar

The sidecar channel of MoeLog: protocol, transport, daemon and CLI.

Do not install this directly. It comes as a dependency of @moecorp/moelog-node and @moecorp/moelog-bun.

What it is

It holds both ends of the channel: the client the SDK uses and the process that listens.

Your app does no networking. It writes NDJSON to a unix socket and returns. A separate process — launched detached, outliving the app — persists, retries and forwards to the server.

That is what makes it possible to report three things no in-process SDK can:

  • that the app died from a SIGKILL or a kernel OOM (reporting it would require being alive),
  • that its event loop is blocked (reporting it would require the very loop that is blocked),
  • that the app never even started.

Measured with the server switched off: emitting five errors cost the app 0.62 ms, and all five arrived on their own once it reconnected.

CLI

Installing either SDK makes the moelog binary available:

moelog run -- bun run index.ts   # supervise: the only way to see "it never started"
moelog status                    # sidecar status and upstream queue
moelog tail -n 20                # latest events
moelog alerts -n 20              # crashes, blocks, failed startups
moelog stop

The sidecar is one single process, shared by every runtime: it owns a socket, and two different versions fighting over it would be an expensive bug to debug.

License

AGPL-3.0-only.

Note that this SDK is imported into your application, so the AGPL's copyleft reaches further here than it would for a server-only project. If that is a problem for your use case, open an issue: a permissive license for the SDKs with AGPL kept for the server is under consideration.