Add Flatpak support - #45
Merged
Merged
Conversation
arximus88
added a commit
that referenced
this pull request
Aug 14, 2026
… guard Adds an Unreleased entry crediting @blossomlabs-gh for #45, and a truth-table case pinning shouldRelaunchUnderX11 to false under Flatpak — the guard exists because re-exec'ing Electron through zypak's spawn interception segfaults.
arximus88
added a commit
that referenced
this pull request
Aug 14, 2026
…t the tag Both files were installed from the cloned git source, so every edit to them sat unused until the release after it — the invalid Categories value fixed in #45 and the screenshot URLs fixed since would both have shipped a release late. They now come from the manifest directory like package.json already does, overwriting what the checkout brought in.
Owner
|
Thanks for pushing it. I was try to delay dealing with Flatpack) |
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
2 participants
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
echo 'TODO: build commands not yet implemented') with a real, verified offline build pipeline.flatpak/package.json+package-lock.json, a build-only npm dependency set (vite/svelte/electron toolchain, no Playwright/Biome/electron-builder) so
flatpak-node-generatorcan vendoreverything Flathub's network-less build needs, including the Electron 43.3.0 binary itself.
flatpak/generated-sources.json(233 vendored sources) generated from that lockfile.npm install->vite build-> offline prodnpm installindist/-> unzipthe vendored Electron binary into
/app/main-> dropdist/into/app/main/resources/app(Electron's default app-loading convention) -> install desktop/icon/metainfo files.
electron-builderinside the sandbox, it fetches its own auxiliarytooling (app-builder etc.) from GitHub at build time, which isn't vendorable offline the way
flatpak-node-generatorhandles theelectronpackage itself.Categories=...;Design;...value in the.desktopfile (flagged byappstreamcliduring export;Designisn't a registered category).build-dir/and.flatpak-builder/, flatpak-builder's local build output.Test plan
flatpak-builder --user --force-clean build-dir flatpak/app.borys.FigmaLinuxNext.ymlbuildsclean against a local working-tree source (offline, after vendoring)
flatpak-builder --user --install ...installs successfullyflatpak run app.borys.FigmaLinuxNextboots under zypak: IpcRegistry seals with all 69channels, MCP server comes up on
127.0.0.1:3845