How zabrodsk/partydeck works
Partydeck is a browser-based multiplayer card-night app: players create or join a room, invite others, and play poker or blackjack from private phones, optionally alongside a shared table display. The Node server is the documented live runtime; it owns rooms, rules, profiles, and filtered game views. A separate experimental Worker/D1 adapter restores room state across requests. The graph retains the documented profile, invitation, display, and motion capabilities; the excerpts do not show every route or client request, so unsupported connections are omitted.
Main entry points: index.js HTTP and events · rooms.js Room lifecycle · app.js Table UI · auth.js Authentication
Components 18
Browser experience
- Table UI
public/app.js - Betting controls
public/betting.js - Card motion
public/motion.js
Node runtime
- HTTP and events
server/index.js - Asset delivery
server/assets.js - QR invitations
server/qr.js - Authentication
server/auth.js - Profiles and stats
server/storage.js - SQLite state
server/storage.js
Game domain
- Room lifecycle
server/rooms.js - Hold’em rules
server/rooms.js - Blackjack rules
server/blackjack.js
Worker adapter
- Worker HTTP adapter
worker/index.js - D1 persistence
worker/database.js - Restored room state
worker/room-state.js
Other components
- Players
- WorkOS AuthKit
- Cloudflare D1
Connections 20
- Players → Table UI: play through
README.md - Table UI → Betting controls: uses controls
public/app.js - Table UI → Card motion: animates cards
public/app.js - Table UI → HTTP and events: HTTP actions
README.md - HTTP and events → Asset delivery: serves assets
server/index.js - HTTP and events → QR invitations: generates QR
server/index.js - HTTP and events → Authentication: routes sign-in
server/index.js - Authentication → Profiles and stats: resolves identity
- Authentication → WorkOS AuthKit: PKCE sign-in
server/auth.js - HTTP and events → Room lifecycle: handles room actions
server/index.js - Room lifecycle → Hold’em rules: runs Hold’em
server/rooms.js - Room lifecycle → Blackjack rules: uses blackjack rules
server/rooms.js - Room lifecycle → Profiles and stats: updates statistics
- Profiles and stats → SQLite state: reads and writes
server/storage.js - Players → Worker HTTP adapter: Worker requests
README.md - Worker HTTP adapter → D1 persistence: handles API state
worker/index.js - D1 persistence → Restored room state: hydrates and mutates
worker/database.js - Restored room state → Room lifecycle: reuses room rules
worker/room-state.js - Restored room state → Blackjack rules: restores blackjack
worker/room-state.js - D1 persistence → Cloudflare D1: persists records
README.md