Conversation
loadFile(file://) breaks root-relative /_next/, /splash.png, and /routes. Bind a minimal 127.0.0.1 static server to the renderer out/ directory and loadURL(http://127.0.0.1:<port>/) when packaged. Bump to v0.8.7. Made-with: Cursor
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
1 participant
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.
Problem
Packaged builds used
BrowserWindow.loadFile()for the Next static export. Underfile://, root-relative assets (/_next/static/...,/splash.png) resolve to the filesystem root, so CSS/JS never load and the UI appears as unstyled HTML.Fix
When packaged, start a minimal HTTP server on 127.0.0.1 (random port) serving
renderer/out/, thenloadURL(http://127.0.0.1:<port>/). Same pattern as dev (HTTP origin). Server closes onbefore-quit.Version
0.8.7 — publish new AppImage / .deb after merge.
Made with Cursor