docs: add Electron live updates guide#18307
Open
riderx wants to merge 2 commits into
Open
Conversation
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.
What changed
Adds an Electron Live Updates page under the Quasar CLI Vite Electron docs and links it from the Electron mode menu.
The page covers:
@capgo/electron-updaterpackage insrc-electronnotifyAppReady()from the rendererWhy
Quasar Electron users currently have build and publishing docs, but no focused guide for renderer-only live updates. This documents the self-hosted/manual pattern without requiring a hosted account.
Validation
pnpm lint:checkNote: local commands emitted workspace Node engine warnings because this machine is running Node v25.9.0, while several Quasar packages request Node 22/24/26+ ranges. The final lint check passed.