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 🙏

© 2024 – Pkg Stats / Ryan Hefner

meck

v0.1.1

Published

Small and type safe message bus with well module separation

Downloads

8

Readme

Meck

Small and type safe message bus with well module separation.

Install

$ npm install meck
# or
$ yarn add meck

Concept

Meck has two concepts - event and command. Event indicates something is happened which has a name with any form of payload. For example, file system watcher's event can be an event on Meck. Command is similar to event because it has a name and a payload too but it is more directive. For example, saving a file can be a command on Meck.

The relation of event and command is similar to input and output. In fact, we input some data with event, then process it and may output the result with command in Meck. This helps you to separate input and output logic.

Usage

Declare Events and Commands

At first, you should declare your events and commands types. You need some object interface that has available event name as a key and its payload type as a value. For example, if you want to declare an event which is named fileChanged with { path: string } payload:

interface Events {
  fileChanged: { path: string }
}

You declare a commands type as same as the events type. The below example is declaring saveFile command which has a object payload including { count: number } property.

interface Commands {
  saveFile: { content: string }
}

Implement EventObserver and CommandEmitter

Next, you should implement EventObserver and CommandEmitter. EventObserver listens some events while CommandEmitter dispatches some commands. The constructors of both class will receive a callback having a parameter of function. In the callback you write a bridge between Meck and external modules. For example, you port some events when external module provide some events in the EventObserver while you observe some commands and notify them to external ones in CommandEmitter. Note that you should pass the events and commands types as a generic type to specify available events and commands.

import { EventObserver, CommandEmitter } from 'meck'

const fileEvents = new EventObserver<Events>(emit => {
  fs.watchFile('test.txt', () => {
    emit('fileChanged', {
      path: 'test.txt'
    })
  })
})

const fileCommands = new CommandEmittter<Commands>(observe => {
  observe('saveFile', payload => {
    fs.writeFileSync('log.txt', payload.content)
  })
})

Generate MessageBus

Then, you generate MessageBus instance which gather all events and commands on one place.

import { MessageBus } from 'meck'

const bus = new MessageBus([fileEvents], [fileCommands])

// Observe event
bus.on('fileChanged', payload => {
  // Emit command
  bus.emit('saveFile', {
    content: 'changed: ' + payload.path
  })
})

License

MIT