mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #15880] issue: Can't build frontend in 0.6.17+ #56369
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @drupol on GitHub (Jul 19, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15880
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
0.6.17
Ollama Version (if applicable)
No response
Operating System
NixOS
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
The frontend should build
Actual Behavior
I maintain
open-webuiin Nix and when building the frontend, I get the error with 0.6.17 only:This error was not present in 0.6.16
Steps to Reproduce
See PR https://github.com/NixOS/nixpkgs/pull/426731#issuecomment-3092525163
Logs & Screenshots
See previous paragraph.
Additional Information
No response
@tjbck commented on GitHub (Jul 19, 2025):
Please read the changelogs,
npm install --forceis required for the time being.@drupol commented on GitHub (Jul 19, 2025):
I will try.
@drupol commented on GitHub (Jul 19, 2025):
Fixed by adding:
@tjbck commented on GitHub (Jul 19, 2025):
Keeping this open for other folks.
@aqeelat commented on GitHub (Sep 2, 2025):
The issue is partially related to some
@tiptappackages stuck on v2 while others are on v3.This is the change log for the affected packages. They have breaking changes. https://github.com/ueberdosis/tiptap/blob/develop/packages/extension-bubble-menu/CHANGELOG.md#301
I'll try to upgrade it and open a PR.
@tjbck commented on GitHub (Sep 2, 2025):
@aqeelat please read our changelogs and comments above. Upgrading will break our interface.
@aqeelat commented on GitHub (Sep 2, 2025):
@tjbck I was just about to mention you. In your commit
da91aba10fyou said that it would break the ui and that we should wait for some fixes. Is there a tracker for that?@tjbck commented on GitHub (Sep 2, 2025):
@aqeelat currently not a high priority. This "issue" is purely cosmetic.
@aqeelat commented on GitHub (Sep 2, 2025):
@tjbck do you mind if I work on it?
@Classic298 commented on GitHub (Apr 3, 2026):
--force is no longer required as of recently, this can be closed