view_node_Script

view_node_Script is the display-node sibling of IO_node_Script from the same pack - same idea of indexing every node class in your ComfyUI install, but wired up as something you drop at the end of a chain to actually look at, rather than something that feeds into more nodes.

The giveaway is is_output_node: true. In ComfyUI that flag marks a node as a terminal - the kind that renders something on the canvas rather than passing data further down the graph, the same category ComfyUI's built-in Preview Image and Preview Text nodes live in. Pair that with the fact it takes an ANY wildcard input plus a free-form multiline data field, and the shape of the thing becomes pretty clear: it's a scratchpad you can plug literally anything into - a STRING, a number, whatever's coming off some other node's output - and see it rendered right there on the node, instead of routing it through a Show Text node or opening the browser console to check what a value actually is mid-workflow.

It also shares the exact same selected_node dropdown as IO_node_Script: pick any of the roughly 1,194 node classes registered across your whole ComfyUI install (not just this pack), and the node reports back a node_source STRING output - again, the reasonable read is "which module owns this node class," useful for the same IMPORT FAILED-hunting and unfamiliar-workflow situations covered in that article. What's different here is you don't need a downstream node to see the result; view_node_Script shows it inline because it's an output node itself.

Put together, this reads as Apt_Preset's combined debug tool: dump arbitrary graph data onto the canvas for a quick look, and look up which extension a given node class belongs to, all from one widget instead of juggling separate Show Text and node-inspector tools. As with IO_node_Script, the pack's own node_description field for this one is empty - nothing in the README walks through it by name - so this is inferred from the schema, not quoted from documentation. If you find yourself needing precise confirmation of exactly what gets written into node_source for a given selection, the honest answer is that you'll learn it faster by dropping the node into a graph and trying it than by reading anything currently published about it.

Installing it. No separate step from the rest of the pack - search "ComfyUI-Apt_Preset" in ComfyUI Manager, or clone it by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/cardenluo/ComfyUI-Apt_Preset.git

Run install.bat on Windows for the Python dependencies, then restart. Since this node is pure introspection with no model weights and no GPU work involved, if the pack imports cleanly at all, this node should just work.

Troubleshooting. The one real, sourced failure mode for this pack is an install-time IMPORT FAILED - there's a documented case on r/comfyui of exactly that happening to ComfyUI-Apt_Preset because of a missing downstream dependency (a ShowText node from a different pack). If view_node_Script - or anything else from Apt_Preset - isn't showing up in your node list, check the ComfyUI startup console for the actual traceback rather than assuming this specific node is at fault; the fix is almost always installing whatever package the log names, via Manager's "install missing custom nodes" or a manual pip install, then a restart. And the same limitation as its sibling node applies: newly installed extensions generally need a full ComfyUI restart before they show up as choices, a live refresh inside the node won't pick them up.