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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@gregoriusrippenstein/node-red-contrib-flowcompare

v0.2.0

Published

Compare editor flow with the flow deployed to the server.

Readme

FlowCompare

FlowCompare node is a node for visually comparing the editor flows with flows deployed to the server.

Flows are deployed from the editor to the server, hence they can differ. This node highlights changes that have occurred in the editor.

Why?

I wanted to have a visual comparison between versions of flows. Also I wanted changes to be classified as being either visual or textual: visual changes movements of nodes, textual are content changes. Node-RED does have a diff tool however, for me, this shows too much (all nodes are shown even those that haven't changed) and changes that are visual are shown textually.

Screencast

For more details why this node exists, check out the screencast.

Description

Once installed, node can be accessed via the menu:

(NOTE: You may be required to restart/redeploy Node-RED to access the menu for the first time.)

img

The panel is split into a list of changes, an image visually showing changes and a detailed change panel at the bottom:

img

Clicking the compare button generates the comparison details.

Update: A double click in the listing of changes will now open the edit panel for that node. That is not shown in the above animation.

Iconography

The top box contains all changes that have happened:

img

  • pencil are nodes that have content changes in addition - potentially - to visual changes
  • eye are nodes that have only visual changes
  • ticks are nodes that have been added
  • cross are nodes that have been deleted.

Colourisation

In the image, nodes are colorised:

  • grey/black are deleted nodes
  • green are added nodes
  • green with blue border are moved nodes, nodes that have only changed visually
  • purple nodes have textual, i.e., content changes
  • nodes are highlighted with red-border when change is selected in the change box

img

The slider to the left is the server version, to the right its the local version of the flow.

In the textual diff box:

img

Red are deletions and green are additions, i.e., changes.

Try before you buy

The sidebar can also be previewed in the serverless Node-RED - change something in the preloaded flow and press the compare button before pressing the deploy button.

Not Perfect

  1. Image Zoom

Zoom of comparison image is not perfect since pinch does not work, only the scroll works for zoom. Since scroll is also used to scroll up and down, scroll left and right to zoom image in and out.

Artifacts