ComfyUI Support and non-Next.js and Vercel service-related build

Hello, I am a community plugin developer from the AI open-source project ComfyUI. Thank you for creating this awesome project.
I used my own time to create the ComfyUI-OpenCut plugin so that OpenCut can run within ComfyUI.
You might have seen me or ComfyUI official post tweets about my plugin on X.com:
https://x.com/jtydhr88/status/1952908729776783848
https://x.com/ComfyUI/status/1955305894989926702

When I was implementing this plugin, I found that OpenCut is highly dependent on Next.js and Vercel service-related logic, which are not supported in ComfyUI.
When building the ComfyUI-compatible version of OpenCut, I removed all Next.js and Vercel Service dependencies and built an independent OpenCut version that can run on any server.

The purpose of creating this issue is to seek your opinion: would you be interested in accepting these build and code changes that remove Next.js and Vercel Service dependencies? Or perhaps as two parallel build approaches?

With ComfyUI's powerful workflow capabilities, we can implement almost any AI-related functionality. As a prerequisite for future support (if you agree), another suggestion is that for calling certain external functions, I recommend implementing them through interface or API methods - for example, subtitle extraction, or future AI-related functions like video background removal.
(Of course, it's completely fine if you disagree - I will maintain it in my own fork.)

Additionally, although I am a member of Comfy Org, my development of this ComfyUI-OpenCut is a personal open-source project and personal initiative, and does not represent ComfyUI Org officially.

No files, tests, or entry points are identified. First review the existing Next.js and Vercel-dependent build described in the issue and clarify whether an independent server build or parallel build approach is wanted; done would be an agreed scope and implementation path.