docs: correct the development and logging pages against the Vite proxy, the build config and the JSON log formatters - #1421
Open
silentoplayz wants to merge 1 commit into
Conversation
silentoplayz
force-pushed
the
docs/development-logging-pages
branch
2 times, most recently
from
September 25, 2026 05:40
bc7520f to
0ecaaf4
Compare
…y, the build config and the JSON log formatters
silentoplayz
force-pushed
the
docs/development-logging-pages
branch
from
September 25, 2026 05:48
0ecaaf4 to
8e102f0
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
I compared the development and logging pages with the frontend build config, the dev scripts and the log formatters.
package.jsonallows Node.js up to 22.x, and the locked dependencies (pdfjs-distamong them) need 20.19 or later, so the requirement is 20.19+ on Node 20 or 22.13+ on Node 22 rather than 22.10 and up. The LAN-testing steps keep theCORS_ALLOW_ORIGINstep: the Vite dev server proxies/api,/ollama,/openai,/oauthand/ws, but Socket.IO still checks the browser'sOriginagainst that list (WEBUI_BACKEND_URLpoints the proxy elsewhere). Ports are changed withPORTandnpm run dev:5050(plus that port's origin inCORS_ALLOW_ORIGIN), not by editing config files. With no backend, the page redirects to a "Backend Required" error page rather than waiting, and/docsis served only withENV=dev.console.log,console.debugandconsole.errorunless built withENV=dev, so the frontend section now says so. The JSONerrorfield is an object withtype,messageandstacktrace, and the top-levelstacktraceonly appears on the few lines written before the Loguru sink starts. An unrecognisedGLOBAL_LOG_LEVELfalls back toINFO, andSRC_LOG_LEVELSis a legacy placeholder.Related issue or discussion
None.
Checklist
Notes for reviewers
Sources on
dev:package.json(engines, scripts),vite.config.ts(proxy,esbuild.pure),backend/dev.sh,main.py(docs_url),src/routes/+layout.svelteandsrc/routes/error/+page.svelte,utils/logger.py, andenv.py(JSONFormatter,GLOBAL_LOG_LEVEL,SRC_LOG_LEVELS).