Dictionary to Console

WAS's README describes this one directly: "Print a dictionary input to the console." No fanfare, no visible output on the canvas - a dictionary goes in, and its contents get printed to the server console at the point in the graph where you dropped the node.

The reason it's worth having: WAS Node Suite quietly builds out a whole dictionary-manipulation subsystem alongside its more visible image and text tools. The README documents Text Dictionary New, Text Dictionary Update (merge two dictionaries), Text Dictionary Get (pull a value out by key), Text Dictionary Convert (turn plain text into a dictionary object), Text Dictionary Keys, and Text Dictionary To Text - a whole small toolkit for building up structured data inside a workflow that otherwise deals almost entirely in flat strings, numbers, and images. The problem with any of that is the same problem you get with booleans and numbers: a dictionary being assembled or merged across several nodes isn't something you can eyeball just by looking at the graph. You can't tell from the wires alone whether a merge actually kept the keys you expected, or whether a "convert text to dictionary" step parsed correctly.

Dictionary to Console is how you actually check. Drop it after a Text Dictionary Update or Text Dictionary Convert step, run once, and read the dictionary's actual contents in your log instead of assuming the merge or parse went the way you intended. It's especially useful mid-pipeline - you don't have to wait until a dictionary-driven value causes a visible problem three nodes later; you can verify the data shape at the exact step where it's built.

Same caveat as every "to Console" node in this pack: this prints to the server console, not the browser UI. Running locally, check your terminal. Running on a hosted platform, check your run logs - there's nothing to see on the canvas itself.

Input is a DICT; there's no meaningful graph output beyond, at most, a pass-through of the same dictionary - the value here is entirely in what shows up in your log, not anything downstream consumes.

Installing it: ComfyUI Manager, search "WAS Node Suite," install, restart - the simplest route. Manual install: cd ComfyUI/custom_nodes && git clone https://github.com/WASasquatch/was-node-suite-comfyui, then pip install -r requirements.txt (portable: python_embeded\python.exe -s -m pip install -r requirements.txt; manual/venv: activate the venv first), restart ComfyUI. No model, no special dependency - it's a print statement, nothing more.

Where it bites: virtually nowhere on its own, since it has no external moving parts to fail. The real risk, as with every node in this pack, lives one level up: WAS Node Suite has been unmaintained since December 2023 (its README says "Retired" outright), and the community's recurring, well-documented complaint is the entire suite failing to import after a ComfyUI or Python update, not individual debug nodes breaking in isolation. If Dictionary to Console vanishes from your node list, check your startup console for a whole-suite import error before assuming this specific node is the problem.