2 Commits

Author	SHA1	Message	Date
Evan Pelle	a7f992e9b0	refactor: convert to npm-workspaces monorepo (engine/core-public/shared/client/server) ... Restructure the single src/ tree into an npm-workspaces monorepo under packages/, rename core -> engine, extract a types-only core-public layer, and break the pre-existing engine -> client dependency cycle. Structure (packages/): core-public public API/wire schemas + shared enums (clean leaf) shared framework-agnostic helpers (clean leaf) engine deterministic simulation (was src/core) client rendering/UI (was src/client) server coordination (was src/server) Dependency DAG: engine -> {core-public, shared}; client -> {core-public, shared, engine}; server -> {core-public, engine}. - npm workspaces: root package.json workspaces + per-package package.json; tsconfig.base.json holds shared options + path aliases (core-public/* shared/* engine/* client/* server/*) resolved uniformly by tsc, Vite (resolve.tsconfigPaths), Vitest, and tsx. Lockfile regenerated. - core-public: moved Schemas/ApiSchemas/CosmeticSchemas/StatsSchemas/ ClanApiSchemas/WorkerSchemas/Base64/PatternDecoder; extracted the enums (GameTypes), GameEvent type, emoji table, and GraphicsOverrides schema. Engine re-exports the moved enums/types so existing imports keep working. - Broke engine -> client cycle: - renderNumber/renderTroops -> shared/format - NameBoxCalculator moved into engine - username validation returns translation key + params; client translates - applyStateUpdate moved to client (operates on the render-only PlayerState) - Config/UnitGrid/execution-Util/GameImpl now use structural read interfaces (engine/game/ReadViews: PlayerLike/UnitLike/GameLike) instead of importing client view classes; client imports view classes from a new client/view barrel; deleted the engine/game/GameView re-export shim. - Build/deploy updated: vite.config, index.html, eslint, Dockerfile (copies packages/ + tsconfig.base.json before npm ci), .vscode, tests. Verified: tsc --noEmit clean; 1364 + 65 tests pass; production vite build succeeds; engine has zero client/server imports; core-public and shared are dependency leaves. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-10 16:51:03 +00:00
Himansu Rawal	e1d31ef1ee	fix: replace setInterval with recursive setTimeout in Master.ts to pr… (#2869) ... If this PR fixes an issue, link it below. If not, delete these two lines. Resolves #2868 ## Description: This PR addresses a critical memory leak in the Master server process (causing ~30GB RAM usage). The issue was caused by `setInterval` calling `fetchLobbies()` every 100ms. When `fetchLobbies` took longer than 100ms to complete (due to network latency or load), requests would pile up indefinitely, creating a massive queue of pending Promises and open sockets. I have refactored the polling logic into a generic `startPolling` utility (in `src/server/PollingLoop.ts`) that uses a recursive `setTimeout` pattern. This ensures that the next `fetchLobbies` call is only scheduled *after* the previous one has completed (successfully or failed), preventing any request pile-up. ## Please complete the following: - [x] I have added screenshots for all UI updates (N/A - backend only) - [x] I process any text displayed to the user through translateText() and I've added it to the en.json file (N/A - no user facing text) - [x] I have added relevant tests to the test directory (`tests/PollingLoop.test.ts`) - [x] I confirm I have thoroughly tested these changes and take full responsibility for any bugs introduced ## Please put your Discord username so you can be contacted if a bug or regression is found: codimo	2026-01-14 09:50:43 -08:00