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

bare-sidecar

v0.5.2

Published

Start and manage Bare sidecar processes from Node.js and Electron

Readme

bare-sidecar

Start and manage Bare sidecar processes from Node.js and Electron. A sidecar is a separate Bare process spawned from a host runtime, with a dedicated IPC channel exposed as a duplex stream on both ends.

npm i bare-sidecar

Usage

In the host process:

const Sidecar = require('bare-sidecar')

const sidecar = new Sidecar(require.resolve('./entry'))

sidecar
  .on('exit', (code, status) => {
    // The sidecar process exited
  })
  .on('data', (data) => {
    // Received data from the sidecar over IPC
  })
  .write('Hello sidecar')

In the sidecar entry (entry.js), the IPC channel is available as a stream on Bare.IPC:

Bare.IPC.on('data', (data) => Bare.IPC.write(data))

API

const sidecar = new Sidecar(entry[, args][, options])

Spawn a bundled Bare runtime running entry and return a Sidecar. entry is the path to the module to run, typically resolved with require.resolve(). args is an array of additional command line arguments passed to the process. options is reserved for future use.

Sidecar extends a duplex stream. Writing to the stream sends data to the sidecar over its IPC channel, and data received from the sidecar over the same channel is emitted as 'data' events. Destroying the stream kills the sidecar process.

The correct prebuilt Bare binary for the current platform and architecture is selected automatically and made executable on first use.

sidecar.stdin

The writable standard input stream of the underlying process.

sidecar.stdout

The readable standard output stream of the underlying process.

sidecar.stderr

The readable standard error stream of the underlying process.

event: 'exit'

Emitted when the sidecar process exits, with the arguments code and status. code is the exit code, or null if the process was terminated by a signal. status is the signal name that terminated the process, or null if it exited normally.

event: 'close'

Emitted after the sidecar process has exited and the stream has been destroyed.

License

Apache-2.0