📦 Dependency Installer

You loaded a Shima workflow, the Dependency Generator printed its manifest, and now you need the actual files. That's the Dependency Installer's side of the bargain: it takes a dependency JSON (either typed in directly or wired from the Generator) and drives an interactive UI that lets you see what's missing and pull it down. Where the Generator is the packing list, this is the guy who actually goes shopping.

Let me be straight about what it does today, because the docs and the code disagree a little. The documentation describes an interactive installer with size-verified downloads and custom save paths via Shima's AssetManager. The backend implementation currently on disk is a lot more modest: it takes json_data (STRING, multiline, default {}) or the optional json_stub wire, and if a stub is connected it takes priority over the typed data, then passes the JSON through and shows it in the UI. The heavy lifting lives in the frontend (dependency_installer.js), which is where the verify-and-install experience happens. So: it's a working pass-through plus a UI hook, and the polished installer described in the docs is the direction of travel rather than the complete current state.

Inputs:

• json_data (STRING) - the manifest, pasted in.
• json_stub (STRING, optional) - wire the Dependency Generator's output here and it overrides json_data for the run. This is the pairing you actually want: Generator → Installer, no copy-paste.

Output: json_out (STRING), the manifest echoed back out, which is handy if you want to pass it to another tool or log it. It's an output node, so it always executes.

The practical flow: run the Generator, feed this node, hit queue, and the UI shows you the dependency list with install buttons per asset. It's still the fastest path from "workflow with missing models" to "workflow that runs," and unlike eyeballing a red graph node-by-node, it gives you one organized checklist.

Two real-world notes. First, the URLs in a Generator-produced manifest start as INSERT_URL_HERE placeholders, so the Installer can only auto-download entries whose URL field was actually filled in - for a fresh workflow you'll be supplying sources for at least some assets. Second, anything that involves downloading files runs whatever code the pack ships, so treat manifests from strangers the way you'd treat any third-party download list: verify the URL before clicking. The pack's own docs frame marketplace syncing as the safe path; hand-typed URLs from an unknown workflow deserve a glance first.

Install with ComfyUI Manager (search "Shima") or

cd ComfyUI/custom_nodes
git clone https://github.com/KDB-USJP/shima_wf

then restart. No models ship with it - its entire purpose is getting models onto your disk.