mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 19:38:46 -05:00
[GH-ISSUE #16455] issue: NPM install Errors #33439
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 @Jeremy-Developer-Page on GitHub (Aug 10, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16455
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
0.6.21
Ollama Version (if applicable)
0.11.4
Operating System
macOS Sonoma, Ubuntu 25.04, Windows
Browser (if applicable)
Safari, MS Edge, Chrome
Confirmation
README.md.Expected Behavior
To have no vulnerabilities during the running of the command npm install
Actual Behavior
13 vulnerabilities (6 low, 7 moderate)
BUT TO FIX THE BUG I'VE A SOLUTION (BUT IF YOU WANT TO TEST IT OUT MORE DO IT, OBV)
I've upgraded the requirements in package.json and now my upgraded version is:
ADDICTIONALLY
To solve a bug that I've see during the launch
ERROR: peewee.OperationalError: unable to open database fileI've edit the env.py file With this add in line 223
So I hope that this feedback will be taken into consideration and possibly implemented in future versions of Open-WebUI.
Steps to Reproduce
Compile the code following the instructions
Logs & Screenshots
Additional Information
Thanks for the consideration and have a great day
@tjbck commented on GitHub (Aug 10, 2025):
Please read the changelogs,
--forceis required for the time being.@Jeremy-Developer-Page commented on GitHub (Aug 10, 2025):
Yeah but the tag --force not solve this problems.
In any case, if you do not wish to accept the feedback, I am sorry but there is nothing I can do about it, so have a nice day. If, on the other hand, you decide to implement the changes I suggested above, I will be happy to have been of assistance.
@traumschule commented on GitHub (Oct 19, 2025):
To install from docs we need to read the changelogs?
@Classic298 commented on GitHub (Oct 19, 2025):
@traumschule this was a temporary issue which was mentioned in the changelogs during that time where some packages would create problems, but using --force from a clean install would fix it
@rgaricano commented on GitHub (Oct 19, 2025):
yes, for solve this:
(I'm also have to add
"y-protocols": "^1.0.6",& change for node 23 inpackage.jsonbefore build it...now i have a script to do it)@traumschule commented on GitHub (Oct 19, 2025):
Well, i hope you solved the underlying issue because
--forceis never a clean solution.