Skip to content

package app for microsoft store (msix) #4

Description

@draylegend

Context

Electrobun (v1.18.1) has zero built-in support for Windows Store distribution — confirmed by grepping node_modules/electrobun/src/cli/index.ts (no matches for msix, appx, partner center, sideload) and the full docs site. Its Windows packaging pipeline only produces a custom self-extracting Setup.exe + .tar.zst + .metadata.json, zipped — not an MSIX/APPX package.

To ship via the Microsoft Store, the build output needs to be wrapped externally, on top of Electrobun's own build, not through it.

What's needed

  • A Partner Center developer account (one-time fee: ~$19 individual / ~$99 company)
  • Package the built app (build/stable-win-x64/letora-Setup.exe + its contents, or the raw app files before zipping) into an MSIX package — likely via the MSIX Packaging Tool or MakeAppx.exe, using the Desktop Bridge approach for a classic Win32 app
  • An app manifest (AppxManifest.xml) with identity/capabilities matching the Partner Center reservation
  • Decide on signing: MSIX packages submitted through the Store can be re-signed by Microsoft on submission, so a self-owned cert isn't strictly required for that channel (unlike sideloaded MSIX, which does need a trusted cert) — worth confirming against current Partner Center docs when this is picked up
  • A CI step (or manual process, at least initially) that runs after electrobun build --env=stable to produce and upload the .msix/.msixbundle to Partner Center

Scope

Store distribution only. GitHub Releases distribution (unsigned .zip) is handled separately in #3 and does not block this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featNew feature or request

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions