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

pear-bridge

v1.2.5

Published

Local HTTP Bridge for Pear Desktop Applications

Downloads

1,963

Readme

pear-bridge

Local HTTP Bridge for Pear Desktop Applications

For use with Pear User Interface libraries, such as pear-electron.

Install

npm install pear-bridge

Usage

The application entrypoint needs to instantiate the bridge and pass its info to the Pear User Interface Runtime Library.

The following example is with pear-electron but any compatible Pear UI Runtime Library should work in the same way:

import Runtime from 'pear-electron'
import Bridge from 'pear-bridge'

const runtime = new Runtime()
await runtime.ready()

const server = new Bridge()
await server.ready()

const pipe = runtime.start({ info: server.info() })
Pear.teardown(() => pipe.end())

API

new Bridge(opts) -> bridge

Options

  • mount - String. Mount path for lookups. Given mount = '/ui a URL pathname of /foo would be fetched from /ui/foo.
  • waypoint - String. Catch all HTML file for any unmatched pathnames. Use this for not found screens or in-app routing. Specify relative to mount.
  • bypass - Array. Default ['/node_modules']. Advanced. Mount bypass, allows dependency discovery from application root.

Methods

  • ready() - returns a promise that resolves when the server is listening
  • close() - closes the server

Properties

  • closed - boolean indicating if server is closed
  • opened - boolean indicating if server is opened
  • closing - promise that resolves when server closes
  • opening - promise that resolves when server opens

License

Apache-2.0