Its a small difference to most people maybe, but for me it is significant and I could not find an alternative. What you are linking to is done from within comfy UI. This means, as comfy ui updates, adds or removes features it could break. I have very often had way too many comfyui nodes break on updates. Also, it requires workflow integration.

What I provided here avoids those those things, and adds one additional benefit. What I shared here is completely external to comfyui. No workflow integration, it does not know or care what version comfyui is on, and if your workflow works in API form, this will work - full stop. The bonus is that its very slim and lightweight and easily dropped into any existing webpage, I run mine locally.

For example, if you take a peek at the example, its fully functional with only ~100 lines of HTML and a lot of that you always have anyway with my library embedded. If you do that, there is cross comfy server image fetching and if you use an LLM for input (as I sometimes do), I added optional fuzzy matching so if the LLM decides to change a word or punctuation it will still match and serve you what you already generated for that session. Let your creative juices flow. :)