Skip to content

feat(build): add a standalone mode for deploys with no backend #166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mcdope merged 1 commit into from
Aug 27, 2026
Merged

feat(build): add a standalone mode for deploys with no backend #166

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions .env.standalone
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Standalone build: no backend services configured.
#
# Used for any deploy where this app is served as plain static files and cannot
# reach our signaling server — an itch.io upload, a subpath host, a fork without
# a server of its own. Build with:
#
# npx vite build --mode standalone --base=./
#
# Multiplayer is gated on this being falsy (`main.ts`'s
# MULTIPLAYER_SERVER_CONFIGURED); `updateMultiplayerTabEnabled` then hides the
# tab entirely, so the build never advertises a mode it cannot connect.
#
# This file states intent in one greppable place. It is not a guarantee — Vite's precedence means a .env.standalone.local silently overrides it (measured: the Multiplayer tab came back). Only checking the built artifact holds.
VITE_MULTIPLAYER_SERVER_URL=