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

@tq-bit/node-red-contrib-trace-messages

v2.0.1

Published

Node to track and aggregate messages over your flows

Downloads

10

Readme

Node Red message trace

This module adds two debug nodes to your node-red instance. Both are meant to create a trace from how the message went through your flows. This is especially useful when trying to debug bigger flows.

The idea is as follows:

  • Each time a message starts to flow, a transaction is created
  • This transaction starts with the first node the message passes and ends with the final one
  • Each time, right before the message is passed ahead to the next node, a snapshot is created
  • This snapshot shows the current state of the flow right before the message was passed ahead
  • By looking at transactions and snapshots, you can see how the message went through your flows

By looking at these transactions and snapshots, you're able to keep track of your flow's state.

Node

Usage

Depending on your needs, draw one or both nodes into your flow. Each time a preDeliver hook is triggered, they will start to create a snapshot or build up a transaction

  • The snapshot node will send one message every time any node sends a message
  • The transaction will send once a flow ends. This means when a node has no next node connected to it.

You can either analyze these messages one by one or use a dedicated software to store and display them.

Example transaction

Example Snapshot

Support and Feedback

If you encounter any issues or have any feedback regarding the Node-RED SSE Package, please feel free to open an issue on the package's GitHub repository. I appreciate your feedback and will do my best to address any problems or feature requests.

License

The Node-RED SSE Package is released under the Apache 2.0 license. Please refer to the license file in the package repository for more information.