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

postcard-js

v1.0.0

Published

An abstraction layer over message brokers clients

Downloads

8

Readme

Postcard (Js version)

An abstraction layer over message broker clients

This library, created for both languages Javascript(https://www.npmjs.com/package/postcard-js) and Ruby(https://rubygems.org/gems/postcard_rb), is an abstraction layer over RabbitMQ client. It allows the communication among the microservices, providing functionality for publishing and subscribing events.

The microservices interact through topics created with one of three routing types: Wide, Explicit and PatternMatching.

Each topic may have multiple rooms and, according to the routing type, microservices exchange messages on a different way.

Wide topic

(Under construction!)

Explicit topic

For this kind of topic a message is published on an specific room using its exact name.

// Send a message

let topic = postcard.createTopic({ name: "topic1", routing: Routing.Explicit });

topic.publish({
  room: "room1", 
  payload: "Message for topic1/room1"
});

// Receive a message

let topic = postcard.createTopic({ name: "topic1", routing: Routing.Explicit });

try {
  let room = await topic.createRoom({ name: "room1", autoDelete: true });

  room.subscribe(async (msg) => {
    console.log("[x] Received " + msg.content);
  });
} catch (error) {
  return;
}

Pattern matching topic

Using a pattern matching routing, a microservice subscribe to a room based on matching between a message routing key and the pattern that was used to create that room.

// Send a message

let topic = postcard.createTopic({ name: "topic1", routing: Routing.Explicit });

topic.publish({
  room: "room1", 
  payload: "Message for topic1/room1"
});

// Receive a message

let topic = postcard.createTopic({ name: "topic1", routing: Routing.Explicit });

try {
  let room = await topic.createRoom({ name: "room1", autoDelete: true });

room.subscribe(async (msg) => {
    console.log("[x] Received " + msg.content);
  });
} catch (error) {
  return;
}

Prerequisites

What things you need to install the software

docker 17+
docker-compose 1.19.0+

Development

# Change the directory to the docker development 
cd docker/dev

# Create a .env file with your local application folder
echo "APP_FOLDER=/path-to-your-local/app" > .env 

# Run the services using docker compose
sudo docker-compose up -d

# Try the examples opening new bash(es) with the following command:
# sudo docker exec -it Postcard bash

# The examples folder path into the running container is:
# /usr/src/app/examples

Publish to NPM

# Go to the docker dev folder
cd docker/dev

# Compose the docker containers
sudo docker-compose up -d

# Modify the npm package version on build/src/package.json

# Connect to the Postcard container
sudo docker exec -it Postcard bash

# Move to the application folder
cd /usr/src/app

# Build the new npm
npm run build

# Login to the npm repository
npm login

# Move to the dist folder
cd /usr/src/app/build/dist

# Publish the new version to the npm repository
npm publish

Authors


License

This project is licensed under the MIT License


Acknowledgments