github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #16556] issue: Dependency conflict with @tiptap/core prevents clean installation without --force #33486

New Issue
Closed
opened 2026-04-25 07:24:24 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-25 07:24:24 -05:00
Owner
Copy Link

Originally created by @Miensoap on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16556

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

v0.6.22

Ollama Version (if applicable)

No response

Operating System

macOS sequoia

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

When running npm ci or npm install in the project's root directory for local development,
the command should complete successfully without any dependency resolution errors.

Actual Behavior

The npm ci command fails with an ERESOLVE error due to a peer dependency conflict with @tiptap/core.

The conflict arises because most @tiptap/* packages (like @tiptap/starter-kit) require @tiptap/core@^3.0.7, while @tiptap/extension-bubble-menu requires an older, incompatible version (@tiptap/core@^2.7.0).

This forces local developers to use --force or --legacy-peer-deps to install dependencies, which can lead to a potentially unstable setup. The official Docker build bypasses this issue by using the --force flag, but this hides the underlying dependency problem.

Steps to Reproduce

Clone the repository: git clone https://github.com/open-webui/open-webui.git

Navigate to the project directory: cd open-webui

Attempt to install dependencies cleanly: npm ci

Observe the ERESOLVE error in the console.

Logs & Screenshots

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @tiptap/extension-bubble-menu@2.26.1
npm error Found: @tiptap/core@3.0.7
npm error node_modules/@tiptap/core
npm error   @tiptap/core@"^3.0.7" from the root project
npm error   peer @tiptap/core@"^3.0.7" from @tiptap/extension-blockquote@3.0.7
npm error   node_modules/@tiptap/extension-blockquote
npm error     @tiptap/extension-blockquote@"^3.0.7" from @tiptap/starter-kit@3.0.7
npm error     node_modules/@tiptap/starter-kit
npm error       @tiptap/starter-kit@"^3.0.7" from the root project
npm error   27 more (@tiptap/extension-bold, @tiptap/extension-code, ...)
npm error
npm error Could not resolve dependency:
npm error peer @tiptap/core@"^2.7.0" from @tiptap/extension-bubble-menu@2.26.1
npm error node_modules/@tiptap/extension-bubble-menu
npm error   @tiptap/extension-bubble-menu@"^2.26.1" from the root project
npm error
npm error Conflicting peer dependency: @tiptap/core@2.26.1
npm error node_modules/@tiptap/core
npm error   peer @tiptap/core@"^2.7.0" from @tiptap/extension-bubble-menu@2.26.1
npm error   node_modules/@tiptap/extension-bubble-menu
npm error     @tiptap/extension-bubble-menu@"^2.26.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

Additional Information

This issue appears to be a leftover from the migration from Tiptap v2 to v3.
Updating @tiptap/extension-bubble-menu to a version compatible with @tiptap/core@^3.0.0 should resolve this conflict and allow for a clean installation.

For example, running npm install @tiptap/extension-bubble-menu@latest resolves the conflict locally.
It would be beneficial to update this in the project's package.json for all developers.

Originally created by @Miensoap on GitHub (Aug 13, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16556 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version v0.6.22 ### Ollama Version (if applicable) _No response_ ### Operating System macOS sequoia ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior When running npm ci or npm install in the project's root directory for local development, the command should complete successfully without any dependency resolution errors. ### Actual Behavior The npm ci command fails with an ERESOLVE error due to a peer dependency conflict with @tiptap/core. The conflict arises because most @tiptap/* packages (like @tiptap/starter-kit) require @tiptap/core@^3.0.7, while @tiptap/extension-bubble-menu requires an older, incompatible version (@tiptap/core@^2.7.0). This forces local developers to use --force or --legacy-peer-deps to install dependencies, which can lead to a potentially unstable setup. The official Docker build bypasses this issue by using the --force flag, but this hides the underlying dependency problem. ### Steps to Reproduce Clone the repository: git clone https://github.com/open-webui/open-webui.git Navigate to the project directory: cd open-webui Attempt to install dependencies cleanly: npm ci Observe the ERESOLVE error in the console. ### Logs & Screenshots ``` npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: @tiptap/extension-bubble-menu@2.26.1 npm error Found: @tiptap/core@3.0.7 npm error node_modules/@tiptap/core npm error @tiptap/core@"^3.0.7" from the root project npm error peer @tiptap/core@"^3.0.7" from @tiptap/extension-blockquote@3.0.7 npm error node_modules/@tiptap/extension-blockquote npm error @tiptap/extension-blockquote@"^3.0.7" from @tiptap/starter-kit@3.0.7 npm error node_modules/@tiptap/starter-kit npm error @tiptap/starter-kit@"^3.0.7" from the root project npm error 27 more (@tiptap/extension-bold, @tiptap/extension-code, ...) npm error npm error Could not resolve dependency: npm error peer @tiptap/core@"^2.7.0" from @tiptap/extension-bubble-menu@2.26.1 npm error node_modules/@tiptap/extension-bubble-menu npm error @tiptap/extension-bubble-menu@"^2.26.1" from the root project npm error npm error Conflicting peer dependency: @tiptap/core@2.26.1 npm error node_modules/@tiptap/core npm error peer @tiptap/core@"^2.7.0" from @tiptap/extension-bubble-menu@2.26.1 npm error node_modules/@tiptap/extension-bubble-menu npm error @tiptap/extension-bubble-menu@"^2.26.1" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. ``` ### Additional Information This issue appears to be a leftover from the migration from Tiptap v2 to v3. Updating @tiptap/extension-bubble-menu to a version compatible with @tiptap/core@^3.0.0 should resolve this conflict and allow for a clean installation. For example, running npm install @tiptap/extension-bubble-menu@latest resolves the conflict locally. It would be beneficial to update this in the project's package.json for all developers.
GiteaMirror added the bug label 2026-04-25 07:24:24 -05:00
GiteaMirror commented 2026-04-25 07:24:26 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Aug 13, 2025):

PLEASE check for existing issue before creating a new one #15880

<!-- gh-comment-id:3184011344 --> @tjbck commented on GitHub (Aug 13, 2025): PLEASE check for existing issue before creating a new one #15880
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#33486
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?