-
Notifications
You must be signed in to change notification settings - Fork 7.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Announcement] The frontend will no longer be shipped in the main ComfyUI repo, it will be a separate pip package instead. #7025
Comments
Well this took me hours to setup the other day, now I cant get it to work. so yeah im pretty smashed by this. I could have used it how it was for years. |
Was there any reasons why you can't make the UI repo a Git submodule for this repo instead? I'm not against the core idea of separating out the frontend code but doing it in the way described with a PyPi pip package instead is a bit weird. |
Git submodules would have the same problem since it's moving the problem to another git repo. The reason for it being a pip package is that we already use python packages to manage core ComfyUI dependencies so it seemed like a much easier thing for people to migrate to than all the other solutions including git submodules. We basically needed a way to ship potentially large frontend updates that now contain some binary files (images with workflows attached). Having them continue living in the git repo would be unsustainable. We don't have to change anything in our packaging or updating scripts to make this work so we assume it will be a seamless transition for almost everyone. |
"After this change is merged if you use the desktop build or the standalone package and update using the update/update_comfyui.bat script or the ComfyUI manager everything should continue working as usual." Sorry, but that doesn't work.... |
This change hasn't been merged yet, it will be most likely merged in ~12 hours so if you have issues before that this isn't the problem. |
Ah ok, thx...I just did it manually xD |
Ok folks. I use SwarmUI. Now SwarmUI is broken and will not work due to this apparent "front end missing" thing. It is not enough to just say some kind of "its a separate package, do a pip install thing". I have no clue what you're talking about. What EXACT steps does a person need to take in order to get this up and running again? I'm on windows 11. Am I supposed to "go to the separate project" and somehow install that? No idea what you mean by "After this change is merged". Help! [edit]... I seemed to be able to install the comfyui frontend using a github clone ... although had trouble with the pip install stuff... but somehow... then did an 'update-windows.bat' and after that it sort of seemed to work? I have no clue what i'm doing. |
I download portable with preinstalled nodes and several GB, we have 2025 with very fast internet speeeds, nobody cares about repo sizes. |
We apologize for the abrupt changes. However, if the front end continues to be updated within the repository as before, it's only a matter of time before it grows from tens of GB to TB. Since this structure is not sustainable in the long run, we had to act quickly to address the issue. |
I sure do have comments! I appreciate you devs are really deep into the matrix on this stuff, but us mere end users really struggle with troubleshooting if errors assume so much knowledge. If I might be so bold and suggest writing more instructional error messages that can help guide a less knowledgable person to self-service, I think we'd be super grateful. What am I supposed to do here, what is thie "Request" and where do I lok into it? I'm so lost... |
This should be enough to push people over the edge. It's so aggravating for us less knowledgeable users to figure out all the errors but this update really broke it for me and now and I cant even update or reinstall ComfyUI without errors. Am I ready to tackle these new problems with more hours, possibly days trying to get it to start again? Not sure I have the energy or ambition to. I see so many complaints and others pushing for a new alternative and this might just be enough to get some new alternatives. I don't want to sound unappreciative, I truly am. All I am saying is that ComfyUI has such a steep learning curve on just the errors alone and now we have to deal with new ones, for the moment anyhow. Well good luck to all who are brave enough on to tackle these new problems. |
Resolving this issue is as simple as reinstalling the Additionally, if an error occurs, the ComfyUI will display what command can be used to fix it if there is a problem. Which part are you stuck on? |
Unfortunately, you can no longer go back to the frontend v1.9.1. This is the last frontend where the preview with the checkpoint and Loread Loader worked!!!!!!! This no longer works in the newer versions. For those who can't get the "new" Frontend installation version to work in the portable version, try changing to the ComfyUI directory and in the cmd window enter: D:\Special\ComfyUI_windows_portable\python_embeded\python.exe -m pip install -r requirements.txt |
this is exactly what I did to integrate the frontend. For me it worked. |
waw this broke everything , spending hours already attempting to fix it , the earlier mentioned fixes don't work here. Damm i regret having pressed the update button. For artists / non coders, this is really a pain in the ass and the instructions are totally unclear. A gonna be a fun night thx |
Making the process for the new ComfyUI UI automatic. Opening a venv and running: D:\Ai\ComfyUI\ComfyUI\venv\Scripts\python.exe -m pip install -r requirements.txt does not have to be done manually. The directory structure will have to be changed to what you use, but here are the contents of my comfyUI.bat file: cd/d "D:\Ai\ComfyUI\ComfyUI" echo Checking for repository updates... echo Activating virtual environment... python.exe -m pip install -r requirements.txt echo Checking for pip updates... echo Running the application... pause |
I am leaving the required solution, for people like me, who know only about cmd but have no understanding of Python's specifications or how ComfyUI works.
I sincerely hope that this hint can help in rescuing those who are trapped in confusion and despair. Sorry for poor English. |
or I suppose to check if there's requiremets.txt in your python embeded folder? |
FYI, latest Goto And execute |
Thank you, it worked to me! |
This comment has been minimized.
This comment has been minimized.
After the update, the |
Manual update sadly broke everything for me aswell. While updating I have these issues appearing at the end of the installing / updating process : ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. And when lauching Comfyui : WARNING: The script f2py.exe is installed in 'C:\Users\Roger\Documents\ComfyUI\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\python_embeded\Scripts' which is not on PATH. At the best to finish : Checkpoint files will always be loaded safely. Any idea why the update has broken all these nodes ? It was working fine before. Any help would be much appreciated :-] |
After this update, some of my older workflows don't work anymore. The frontend freezes whenever i try to load them up. The backend still works fine, so i have to close all tabs and restart the frontend with the default worflows. |
You need to downgrade numpy to Execute following commands.
|
Help me :( |
Wow, thanks a lot ! Getting help from you is an honor :-) A big thank you for the rest of your work, it is so HUGE and helpful for the community... |
Why does my pip package get downgraded every time I do an update?
|
new error: mat1 and mat2 shapes cannot be multiplied (308x768 and 4096x5120) |
Due to the frontend being a separate project it doesn't make sense to continue shipping the frontend as part of the main repo.
To make our lives easier and prevent the main ComfyUI repo from becoming too large in size over time we have decided to start shipping the frontend as a separate pip package instead.
#7021
After this change is merged if you use the desktop build or the standalone package and update using the update/update_comfyui.bat script or the ComfyUI manager everything should continue working as usual.
If you update manually using "git pull" you will have to do the extra step of updating the frontend using:
pip install -r requirements.txt
If you have any comments or concerns about this change, let us know.
The text was updated successfully, but these errors were encountered: