Display integer

Sometimes you just want to see what a number actually is in the middle of a graph without dead-ending a wire into a print statement or breaking your pipeline to check. LF_DisplayInteger is the smallest possible answer to that: wire an integer in, it shows up directly on the node's face, and the same value passes straight back out so you can leave the node inline without disrupting anything downstream.

There's exactly one input that matters - integer, defaulting to 0 if nothing's connected - and one output, the same integer value, re-emitted unchanged. It's flagged as an output node, meaning it renders its value in the UI on its own without you needing to route it to a separate save or preview step. The optional ui_widget slot is the display rendering itself (via KUL_CODE), not something you configure.

Where this earns its keep is debugging math-heavy chains - say you're computing a step count or a resolution dimension through LF_MathOperation or LF_ExtractString's result_as_int output, and something downstream is behaving oddly. Splice LF_DisplayInteger into the wire, run once, and you can see exactly what value made it through without adding a separate branch or breakpoint-style node.

It's deliberately the simplest node in this whole pack, and that's the appeal. There's no history, no chart, no fancy widget beyond the plain number display - it doesn't try to be more than a probe. If you find yourself wanting trend tracking across multiple runs rather than a single-run peek, that's outside its scope; this node only ever shows you what happened on the most recent execution.

Installing it. ComfyUI Manager: search "LF Nodes," install, restart. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/lucafoscili/lf-nodes, then restart. Use that repo - comfyui-lf, linked from comfy.icu's node page, is the pack's original home and has been archived since the author's migration; current development is at lf-nodes. No models, no dependencies worth mentioning - this is about as lightweight as a custom node gets.

Where people get tripped up. Honestly, not much - it's a small, single-purpose node. The one thing worth knowing: if you're expecting it to format or transform the number somehow (rounding, padding, unit conversion), it doesn't - it displays exactly what it received, nothing more. If you need type conversion rather than display, look at LF_ExtractString's typed outputs or LF_MathOperation instead. And since it's an output node, don't be surprised if it shows up in the UI's results even on runs where you weren't specifically trying to view anything - that's expected behavior for this kind of always-visible probe node.