NerdGram1337 v1.4.2: Compare, Baselines, and Find and Replace for Mermaid Diagrams
NerdGram1337 is a Mermaid diagramming app I build and maintain, and it runs on your own machine. You write diagrams in Mermaid, you get a live preview, and what you save is a real .mmd file on disk. It's free and MIT-licensed.
You don't need an account, and there's no hosted service or AI generation anywhere in it. v1.4.2 came out on November 15, 2026. (Atlas is the code name for the whole 1.x line, not just this release.)
This post digs into two of the bigger pieces in it: a read-only compare against named baselines and a find and replace that works across the whole workspace. Both first showed up back in v1.2.0. If you're new to the app, the original walkthrough covers the basics. The commands below use v1.4.2.
A few other things are in this release too. Clicking an object in the preview now jumps the editor to the line that drew it. From data builds a diagram from a CSV, JSON, or network JSON file (or from pasted Cisco CDP or LLDP neighbor output) and can refresh it from that file later. There's a token-based REST API at /api/v1 for scripts and CI, and there's optional GitHub sync that copies your diagrams to a private repo in your own GitHub account.
Compare and baselines
If you've ever had to answer "what changed in this diagram since last month?", this is the feature I built for that. You can keep any revision as a named baseline. Named baselines sit outside the usual 20-revision prune, and each diagram can hold up to 20 of them (you can change that cap with NERDGRAM_BASELINE_CAP).
Compare is read-only and never touches the diagram file. It draws one merged picture, colored like this:
- added items in green
- removed items in red and dashed
- changed items in amber
- unchanged items dimmed
Labels stay high-contrast on the colored nodes, so you can still read the text. You also get side-by-side and text views, a legend, and a change summary.
Every diagram type gets a text diff, front matter included. Flowcharts go a step further with a node-and-edge diff that picks up added and removed nodes, relabels, arrow and style changes, and subgraph moves.
The compare picture exports as SVG, PNG, JPG, or PDF, and the change summary exports as Markdown, which is handy for dropping into a change ticket or a pull request.
Workspace find and replace
The editor's find bar still only works on the diagram you have open. Workspace find and replace is its own dialog, and you can open it from the dashboard, the command palette, or the editor find bar.
It shows you a preview first, and you can leave out a whole file or just a single match. Any file that's open in an editor gets skipped, same as any file that changed since the preview, and it tells you what it skipped. It also saves a revision before each change. So if a batch goes sideways, you can undo it.
API and CLI
The new features are on the REST API too, and the nerdgram command-line client can call them with nerdgram diff, nerdgram baseline and nerdgram replace.
Running it
Docker is the simplest way to run the app. In the example below, I publish the port on loopback only.
docker pull ghcr.io/networknerd1337/nerdgram1337:v1.4.2
docker run -d \
--name nerdgram1337 \
--restart unless-stopped \
-p 127.0.0.1:8787:8787 \
-e NERDGRAM_DATA_DIR=/data \
-e NERDGRAM_INSTALL=docker \
-v nerdgram-data:/data \
ghcr.io/networknerd1337/nerdgram1337:v1.4.2
Then open http://127.0.0.1:8787. If you'd rather not pin a version, the :latest tag points at the newest full release.
You can also run it from source with Node.js 20 or newer and npm 10 or newer.
git clone https://github.com/NetworkNerd1337/NerdGram1337.git
cd NerdGram1337
npm run install:all
npm run dev
That starts the development server at http://localhost:5173. For a production build on port 8787, run npm run build, and then npm start instead of npm run dev.
To be clear, the npm package isn't the app. npm install -g nerdgram1337 only installs the nerdgram command-line client, which talks to a running app at NERDGRAM_URL (default http://127.0.0.1:8787) and can't start the app by itself. Get the app running first, then install it.
Still local-first
A Node.js install listens on loopback (127.0.0.1 and ::1) by default, and the Docker example above only publishes the port on 127.0.0.1. Your diagrams stay plain files, and you still don't need an account. It's a code-first editor, so you write Mermaid instead of dragging boxes around a canvas.
The code is on GitHub at NetworkNerd1337/NerdGram1337. What changed in the latest release is in the v1.4.2 release notes. Compare and find and replace are covered in the v1.2.0 release notes, and every release is on the Releases page. If something breaks or you'd like to see a feature, open an issue. And if it's useful to you, a star on the repo helps. There's more on my site at ryanthomashuff.com.
Comments
No comments yet. Start the discussion.