I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Git Clone
Open WebUI Version
v.0.6.18
Ollama Version (if applicable)
v0.9.6
Operating System
ubuntu 24.04
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
build without errors
Actual Behavior
Error building v.0.6.18
error during build:
[vite-plugin-sveltekit-compile] [vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
[vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
at viteWarn (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65757:17)
at onRollupWarning (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65789:5)
at onwarn (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65452:7)
at file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:18686:13
at Object.logger [as onLog] (file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:20325:9)
at ModuleLoader.handleInvalidResolvedId (file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19275:26)
at file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19233:26
Steps to Reproduce
EDITED for correct:
running npm install
npm install --force --legacy-peer-deps
NODE_OPTIONS=--max_old_space_size=4096 npm run build
Logs & Screenshots
error during build:
[vite-plugin-sveltekit-compile] [vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
[vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
at viteWarn (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65757:17)
at onRollupWarning (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65789:5)
at onwarn (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65452:7)
at file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:18686:13
at Object.logger [as onLog] (file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:20325:9)
at ModuleLoader.handleInvalidResolvedId (file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19275:26)
at file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19233:26
Additional Information
(node version v23.8.0 with package.json modificated for support this engine)
SOLVED adding "y-protocols":"^1.0.6",
in Dependencies section of package.json
Originally created by @rgaricano on GitHub (Jul 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15887
### 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
v.0.6.18
### Ollama Version (if applicable)
v0.9.6
### Operating System
ubuntu 24.04
### 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
build without errors
### Actual Behavior
Error building v.0.6.18
```
error during build:
[vite-plugin-sveltekit-compile] [vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
[vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
at viteWarn (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65757:17)
at onRollupWarning (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65789:5)
at onwarn (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65452:7)
at file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:18686:13
at Object.logger [as onLog] (file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:20325:9)
at ModuleLoader.handleInvalidResolvedId (file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19275:26)
at file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19233:26
```
### Steps to Reproduce
EDITED for correct:
running
~~npm install~~
npm install --force --legacy-peer-deps
NODE_OPTIONS=--max_old_space_size=4096 npm run build
### Logs & Screenshots
```
error during build:
[vite-plugin-sveltekit-compile] [vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
[vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
at viteWarn (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65757:17)
at onRollupWarning (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65789:5)
at onwarn (file:///mnt/IAI/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65452:7)
at file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:18686:13
at Object.logger [as onLog] (file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:20325:9)
at ModuleLoader.handleInvalidResolvedId (file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19275:26)
at file:///mnt/IAI/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19233:26
```
### Additional Information
(node version v23.8.0 with package.json modificated for support this engine)
**SOLVED** adding
` "y-protocols":"^1.0.6",`
in Dependencies section of package.json
GiteaMirror
added the bug label 2026-05-13 04:19:51 -05:00
I'm running npm install --force --legacy-peer-deps since time ago because an error with i18n.parser with node 23
<!-- gh-comment-id:3094475094 -->
@rgaricano commented on GitHub (Jul 20, 2025):
I'm running `npm install --force --legacy-peer-deps` since time ago because an error with i18n.parser with node 23
[vite-plugin-sveltekit-compile] [vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/dev/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
[vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/dev/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
at viteWarn (file:///mnt/IAI/dev/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65757:17)
at onRollupWarning (file:///mnt/IAI/dev/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65789:5)
at onwarn (file:///mnt/IAI/dev/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65452:7)
at file:///mnt/IAI/dev/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:18686:13
at Object.logger [as onLog] (file:///mnt/IAI/dev/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:20325:9)
at ModuleLoader.handleInvalidResolvedId (file:///mnt/IAI/dev/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19275:26)
at file:///mnt/IAI/dev/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19233:26
<!-- gh-comment-id:3094707240 -->
@rgaricano commented on GitHub (Jul 20, 2025):
Same building dev branch ... same solution
```
[vite-plugin-sveltekit-compile] [vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/dev/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
[vite]: Rollup failed to resolve import "y-protocols/awareness" from "/mnt/IAI/dev/open-webui/node_modules/y-prosemirror/src/plugins/cursor-plugin.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
at viteWarn (file:///mnt/IAI/dev/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65757:17)
at onRollupWarning (file:///mnt/IAI/dev/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65789:5)
at onwarn (file:///mnt/IAI/dev/open-webui/node_modules/vite/dist/node/chunks/dep-CevzF2vT.js:65452:7)
at file:///mnt/IAI/dev/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:18686:13
at Object.logger [as onLog] (file:///mnt/IAI/dev/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:20325:9)
at ModuleLoader.handleInvalidResolvedId (file:///mnt/IAI/dev/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19275:26)
at file:///mnt/IAI/dev/open-webui/node_modules/rollup/dist/es/shared/node-entry.js:19233:26
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rgaricano on GitHub (Jul 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15887
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v.0.6.18
Ollama Version (if applicable)
v0.9.6
Operating System
ubuntu 24.04
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
build without errors
Actual Behavior
Error building v.0.6.18
Steps to Reproduce
EDITED for correct:
running
npm installnpm install --force --legacy-peer-deps
NODE_OPTIONS=--max_old_space_size=4096 npm run build
Logs & Screenshots
Additional Information
(node version v23.8.0 with package.json modificated for support this engine)
SOLVED adding
"y-protocols":"^1.0.6",in Dependencies section of package.json
@tjbck commented on GitHub (Jul 20, 2025):
#15880
@rgaricano commented on GitHub (Jul 20, 2025):
sorry:
running
npm install --force --legacy-peer-deps(I have it scripted)
@rgaricano commented on GitHub (Jul 20, 2025):
I'm running
npm install --force --legacy-peer-depssince time ago because an error with i18n.parser with node 23@rgaricano commented on GitHub (Jul 20, 2025):
Same building dev branch ... same solution