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 🙏

© 2025 – Pkg Stats / Ryan Hefner

pear-messages

v1.0.5

Published

Receive object messages from a Pear application's processes/threads using object pattern-matching

Downloads

3,202

Readme

pear-messages

Receive object messages from a Pear application's processes/threads using object pattern-matching

Usage

import messages from 'pear-messages'

const stream = messages({ some: 'props' })

stream.once('data', console.log)

Elsewhere in app use pear-message:

import message from 'pear-message'

await message({ some: 'props', to: { pattern: ['match', 'against'] } })

Should log: { some: 'props', to: {pattern: ['match', 'against'] }}

API

messages(pattern[, listener]) -> stream | messages(listener, pattern) -> stream

Listen for application messages sent with pear-message based on pattern which is an object whose properties match a subset of the properties for a given target message.

A function which accepts a pattern object and returns an Iambus subscriber (which inherits from streamx Readable) which emits message objects matching a provided pattern object.

If no pattern object or an empty pattern object is provided all messages will be emitted. A pattern object is an object (typically) containing a subset of matching values for a given target object. Message objects can be user generated or platform generated.

The subscriber stream has a data event which can be listened to, it can also be consumed with for await and an listener function can be passed in addition to pattern (message(pattern, listener)) or as a single argument (messages(listener)) (indicating a catch-all pattern).

A message object may have any properties. Platform-generated messages are given a type property.

The message stream is auto-ended during Pear.teardown.

Examples:

Listen for an internal platform message using a pattern object and listener function:

import messages from 'pear-messages'

messages({ type: 'pear/wakeup' }, ({ data, link }) => {
  console.log('pear/wakeup', data, link)
})

Tiny utility module which logs all messages using for await:

import messages from 'pear-messages'

for await (const message of messages()) {
  if (global.LOGBUS) console.log('BUS:', message)
}

Use message to create an application message:

import message from 'pear-message'
import messages from 'pear-messages'

const ctaClicks = messages({ type: 'my-app/user-cta' })

ctaClicks.on('data', (msg) => {
  console.log('cta click', msg)
})

// elsewhere
onUserClickCta((event, data) => {
  message({ type: 'my-app/user-cta', event, data })
})

License

Apache-2.0