LoRA List

rgthree's Power Lora Loader made the "many LoRAs in one node" pattern famous, and this is this pack's take on the same idea with a twist. HYBS_LoRAList builds a LIST of LoRA filenames from your models/loras folder, and its first row is a NONE baseline that comes out as null. The point of that baseline: you always have a "no LoRA" entry in the list, so a comparison loop can generate the unmodified reference image alongside the LoRA-stacked variants.

It's a list builder, not a loader - it doesn't apply anything itself. It produces filenames; something else (the pack's Load LoRA node, a list-iterating LoraLoader, or a batch wrapper) does the applying. That's the separation of concerns the pack seems to like: the list nodes make data, the loader nodes consume data.

How it works

Like the pack's other list nodes, the single selection input is socketless - an internal widget state you edit by clicking rows. The widget lists every .safetensors in models/loras, and an add lora button grows the list. Two behaviors worth knowing:

• Selecting NONE in the first row makes that slot output null - the explicit no-LoRA baseline.
• Selecting NONE in any later row deletes that row instead. The author's reasoning: the baseline belongs at the front, and a NONE in the middle would just confuse the count.

The backend enforces exactly that: NONE is only allowed in the first row, and validation raises a clear error otherwise. Outputs:

• lora names (LIST) - filenames in row order, with the initial NONE as null
• count (INT) - total entries including the baseline, so you know how many slots you're iterating over

For strengths, the author's docs point you at the pack's Double List node as the companion - a parallel float list, one strength per LoRA row.

Installation

Standard pack install:

cd path/to/ComfyUI/custom_nodes
git clone https://github.com/hybskgks28275/ComfyUI-hybs-nodes.git
pip install -r ComfyUI-hybs-nodes/requirements.txt

Or "ComfyUI-hybs-nodes" via ComfyUI Manager and restart.

Where this earns its keep: A/B and grid comparisons where "LoRA on" and "LoRA off" have to exist side by side, or multi-LoRA stacks you reconfigure often. The baseline-in-the-list design is the differentiator - most stack loaders make the no-LoRA case a separate workflow. If you do disciplined comparisons, that one detail is worth the install by itself.