Replace front proxy with new SvelteKit frontend app
- Remove the old Hono/Bun proxy server - Add the new `apps/frontend` SvelteKit scaffold and telemetry hook
This commit is contained in:
@@ -148,3 +148,15 @@ Update rule:
|
||||
- Split `apps/front` into a thin entrypoint, shared `src/core/utils.ts`, and a dedicated `src/domains/links/{router,service}.ts` flow
|
||||
- Moved link resolve/prepare logic and orchestrator calling into the links domain service so `src/index.ts` only wires middleware and routes
|
||||
- Verified the cleaned `apps/front` app compiles cleanly with `tsc --noEmit`
|
||||
|
||||
### 21 — Frontend Remote Function Migration
|
||||
|
||||
- Migrated the legacy front server-side link flow into `apps/frontend` as SvelteKit remote functions in `src/lib/domains/link/link.remote.ts`
|
||||
- Added frontend request flow IDs in `src/hooks.server.ts` so remote functions build `FlowExecCtx` from `event.locals` consistently
|
||||
- Preserved the two server operations as a query/command split: link resolve remains read-only and session prepare remains the mutating flow that calls orchestrator
|
||||
|
||||
### 22 — Frontend Link Domain Refactor
|
||||
|
||||
- Reduced `apps/frontend/src/lib/domains/link/link.remote.ts` to thin remote-function entrypoints only
|
||||
- Split link-domain server responsibilities into dedicated files: `link.data.ts`, `link.utils.ts`, `orchestrator.service.ts`, and `link.service.ts`
|
||||
- Moved orchestrator calling, link validation shaping, and reusable error creation out of the remote layer for a cleaner domain boundary
|
||||
|
||||
Reference in New Issue
Block a user