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

@n0tify/common

v0.0.10

Published

Library that shares common structures between [client](https://www.npmjs.com/package/@n0tify/client) and [subscriber](https://www.npmjs.com/package/@n0tify/subscriber).

Downloads

2

Readme

@n0tify/common

Library that shares common structures between client and subscriber.

Transport

Defines what service should be used for data exchange.

Example: RabbitMQ, Kafka, Redis and other...

Every transport is constructed individually and passed as param to the client or subscriber.

Transport implementation example

import { Transport } from '@n0tify/common';

class MyTransport implements Transport {
  async connect() {
    console.log('connected');
    return true;
  }

  async disconnect() {
    console.log('disconnected');
    return true;
  }

  send(pattern, data) {
    console.log(`sending data to ${pattern}`, data);
  }

  subscribe(callback) {
    console.log(`subscribed ${callback} for incoming messages`);
  }

  unsubscribe(callback) {
    console.log(`unsubscribed ${callback} from incoming messages`);
  }
}

Channel

Defines which channel should be used for data send.

Example: SMS, Email, Push

Every channel is constructed individually and has it own paramters and ID.

Channel implementation example

Let's imagine simple SMS channel, this is how implementation could look like:

import { Channel } from '@n0tify/common';

type SmsChannelMessageProps = {
  to: string,
  content: string;
}

class SmsChannel extends Channel<SmsChannelMessageProps> {
  // Phone number used to send messages
  from: string;

  constructor(...) {
    this.from = '123456789';
  }

  sendMessage(pattern, data, context) {
    console.log('Message send');
  }

  onMessage(pattern, data, context) {
    console.log('Message received');
  }
}

const smsChannel = new SmsChannel({
  from: '987654321'
});

Further usage

For further usage see client or subscriber.