11 Commits

Include renames

Author	SHA1	Message	Date
Konstantin WohlwendandCursor	b11257fd5b	Re-add Elysia backend transport ... Keep the transport migration isolated on a dedicated branch so development can continue without blocking dev. Co-authored-by: Cursor <[email protected]>	2026-07-13 12:41:55 -07:00
Konstantin Wohlwend	7525526730	Revert "refactor(backend): remove Next.js compat shims, use standard Web APIs (#1652)" ... This reverts commit ae09be9c66.	2026-07-13 12:36:36 -07:00
6 people	ae09be9c66	refactor(backend): remove Next.js compat shims, use standard Web APIs (#1652) ... ## What Removes the Next.js compatibility shim layer that the ElysiaJS backend migration (#1630) introduced, replacing it with standard Web APIs and de-aliased local runtime helpers. Addresses N2D4's review note on #1630: > i think we should create a followup PR which cleans these up and uses the elysia methods directly — so we don't need a nextjs compat layer forever Stacked on `migrate-backend-to-elysiajs`. ## Changes **`next/server` → standard Web APIs (eliminated)** - `NextRequest` → `Request`, `NextResponse.json()` → `Response.json()`, `new NextResponse(...)` → `new Response(...)`, `req.nextUrl` → `new URL(req.url)` - Hot path (`smart-route-handler`) computes `const requestUrl = new URL(req.url)` once - Deleted `lib/next-compat/server.tsx`; rewrote `server/next-request-shim.ts` → `server/backend-request.ts` (`createBackendRequest`, returns a plain `Request`) **`next/headers` + `next/navigation` → `lib/runtime/` (de-aliased)** - `git mv`'d the real runtime helpers (`headers`, `navigation`, `request-context`) out of `lib/next-compat/` into `lib/runtime/`, repointing all consumers to `@/lib/runtime/*` - The cookie/header/redirect mechanism (AsyncLocalStorage + thrown redirect errors, driven by `app.ts`) is unchanged — it was only *named* after Next, never actually Next **Config + cleanup** - Dropped the `next/*` path aliases from `tsconfig.json`, `vitest.config.ts`, `tsdown.config.ts` (removed `nextCompatPlugin`, the alias map, and the `next` bundling special-case) - Deleted `fetch.d.ts` and removed the no-op `next: { revalidate }` fetch option in `changelog/route.tsx` (caching never worked outside the Next runtime) - Converted the unreferenced `proxy.tsx` so it still compiles (it's dead code superseded by `server/middleware.ts` — deletion candidate, left out of this PR) No `next/*` imports remain in the backend. ## Verification - `tsc --noEmit` — passes (exit 0) - `eslint` on all changed files — clean ## Notes / not in scope - This removes the **`next/*` façade**. It keeps the underlying ALS-based request-context mechanism rather than threading Elysia's native context (`set.cookie`, `set.redirect`) into every handler — that's a much larger change touching handler signatures across the whole API surface. - One internal redirect digest string is still `"NEXT_REDIRECT"` (matched in both `navigation.tsx` and `app.ts`); renamable but cosmetic. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Remove the `next/*` compatibility layer and switch the backend to standard Web APIs. This simplifies handlers and config while keeping the ALS request context and redirect behavior unchanged. - **Refactors** - Replaced `NextRequest`/`NextResponse` and `req.nextUrl` with `Request`/`Response` and `new URL(req.url)` across handlers, proxies, health/unsubscribe routes, and IDP endpoints. - Moved runtime helpers to `@/lib/runtime/*` (`headers`, `navigation`, `request-context`) and updated imports. - Added `server/backend-request.ts` to build backend `Request`s with merged headers; removed `server/next-request-shim.ts` and `lib/next-compat/server.tsx`. - Updated proxy rewrite to set `x-middleware-rewrite`; IDP routes now return `Response` directly with 307/308 mapping. - Removed the `next:{revalidate}` fetch option; deleted `lib/next-compat/fetch.d.ts`. - Dropped `next/*` aliases from `tsconfig`, `tsdown`, and `vitest`; route registry/types now use `Request`. - **Migration** - Import from `@/lib/runtime/headers` and `@/lib/runtime/navigation` instead of `next/headers` and `next/navigation`. - Route handlers should accept `Request` and use `new URL(req.url)` for URL parsing. <sup>Written for commit b4a534ff36. Summary will update on new commits.</sup> <a href="https://cubic.dev/pr/hexclave/hexclave/pull/1652?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: mantra <[email protected]> Co-authored-by: Cursor <[email protected]> Co-authored-by: Bilal Godil <[email protected]>	2026-07-09 21:45:15 -07:00
BilalG1andGitHub	609579abab	feat(hexclave): PR 3 — native @hexclave/* source rename + delete dual-publish wiring (#1482)	2026-05-29 15:21:59 -07:00
Konstantin Wohlwend	5a8e0e5112	Small fixes	2026-05-27 18:01:20 -07:00
3 people	f7e389809e	feat(hexclave): PR 1 — wire compatibility layer (invisible) (#1475) ... ## Summary **Stacked on #1468** (`docs/hexclave-rename-plan` — the plan doc). Diff vs that base = the actual PR 1 code. This is **PR 1 of the Hexclave rebrand: the invisible compatibility layer**. Everything is additive. Old SDKs, old wire identifiers, and old env var names keep working unchanged. The backend dual-accepts and dual-emits; new SDK code emits `x-hexclave-*` headers and the `hexclave_` Bearer prefix; cookies dual-write; env vars dual-read across every category. **No user-visible rebranding lands here** — that's PR 2. See [`RENAME-TO-HEXCLAVE.md`](./RENAME-TO-HEXCLAVE.md) → *"PR 1 implementation guide"* for the full per-work-area spec, file pointers, and chosen approach. ## What's implemented (all 14 PR-1 work-areas) - **SDK export aliases** — `Hexclave*` aliases for the user-facing `Stack*` exports added in `packages/template`; codegen propagates them to `@stackframe/{js,stack,react,tanstack-start}`. React-only aliases correctly excluded from `@stackframe/js`. (`e60550a2`) - **JWT issuer dual-accept** — `decodeAccessToken` accepts both `api.stack-auth.com` and `api.hexclave.com` issuers. Signing unchanged. (`fc781def`) - **Request-header dual-accept** — backend + dashboard proxies normalize `x-hexclave-*` → `x-stack-*` at the existing empty proxy hook (so `smart-request.tsx` and every route schema keep working unchanged); CORS allowlists extended via a derive-once helper. (`2a056eac`) - **MCP `ask_hexclave`** — registered alongside `ask_stack_auth` via a shared helper; `ask_stack_auth` behavior byte-identical. (`30ffd604`) - **Dev-tool** — DOM ids + header emit switched. `window.HexclaveDevTool` exposed alongside `window.StackDevTool`. (`32131ea7`) - **The big consolidated commit** (`7fed864a`): - **Env vars** — central `getEnvVariable` prefix-transform (HEXCLAVE first, STACK fallback); dashboard + template client env files dual-read; `turbo.json` globalEnv; `NEXT_PUBLIC_STACK_PORT_PREFIX` renamed outright across ~82 files including docker. - **Cookies** — dual-write/dual-read auth (`stack-access`/`-refresh-*` and custom-domain variants), OAuth-state (`stack-oauth-{inner,outer}-*`), and low-risk cookies (`stack-is-https`, `stack-last-seen-changelog-version`). Bypass sites patched (backend OAuth callback, dashboard remote-dev auth route, impersonation snippets, snapshot serializer). - **Bearer prefix** — SDK token parser accepts both `stackauth_` and `hexclave_`; emits `hexclave_`. Discovery correction: this is purely SDK-internal — the backend never parses it. - **Response headers** — backend dual-emits `x-hexclave-{request-id,actual-status,known-error}`; SDKs dual-read (new first, stack fallback). - **SDK request-header emit switch** — `client/server/admin-interface.ts` + dashboard `api-headers.ts` + `internal-project-headers.ts` + `feedback-form.tsx` switched to `x-hexclave-*`. Plus `stack_response_mode` query param. - **Storage keys** — dev-tool / cli-auth / oauth-button / docs keys renamed (straight); `stack:session-replay:v1` dual-read so in-progress recordings survive SDK upgrades; `stack_mfa_attempt_code` dual-read. - **Query params** — cross-domain params dual-emit/dual-accept via shared helpers; backend `oauth/authorize` accepts `hexclave_response_mode` and `stack_response_mode`; `stack-init-id` renamed. - **`Symbol.for`** — app-internals symbol gets a parallel `Symbol.for("Hexclave--app-internals")` getter on each attach site (no read-site churn — old symbol still attached). 3 file-private symbols renamed outright. - **Config discovery** — prefer `hexclave.config.ts`, fall back to `stack.config.ts` at every discovery site (CLI / dashboard / backend / local-emulator); `init` writes the new filename; CLI credentials path migrates. - **Internal renames** — `StackAssertionError`, `StackClient/Server/AdminInterface` renamed outright (no alias, per the "internal-only → rename" rule). ~264 files touched. - **Review-pass fixes** (`21217fbe`) — three real bugs found by parallel review agents and fixed: - `snapshot-serializer.ts` was interpolating the whole `keyedCookieNamePrefixes` array (`${arr}`) — adding a second prefix would have corrupted **every** OAuth-cookie snapshot, not just new ones. - **Docker port-prefix producer/consumer mismatch** — `entrypoint.sh`/`run-emulator.sh`/cloud-init `user-data` were still producing `NEXT_PUBLIC_STACK_PORT_PREFIX` while the dashboard sentinel + consumers had been renamed; silent self-host regression (custom port prefix would be ignored). - **Missing `hexclave-oauth-inner-*` dual-write** in the OAuth authorize route — callback's fallback masked it but the dual-write was specified by the plan. - Plus: `mcp.test.ts` tool-list assertions updated to include `ask_hexclave`; two dashboard header-emit sites switched to `x-hexclave-*` for consistency. - **E2E snapshot serializer follow-up** (`4b16cc5d`) — `x-hexclave-request-id` added to the hidden-headers list (mirroring `x-stack-request-id` treatment), and 2 sample inline snapshots regenerated in `projects.test.ts` to include the new dual-emitted headers. ## Verification - **`pnpm typecheck`** — clean (the fresh-worktree `@/.source` / Prisma codegen gap in `stack-docs` is pre-existing and unrelated). - **`pnpm lint`** — 29/29 packages green. - **`pnpm exec turbo run build --filter=./packages/*`** — 13/13 packages build (including `@stackframe/stack-cli` once the dashboard standalone is present). - **Live E2E** against a running backend on `cl/hexclave-pr1`: - `pnpm test run apps/e2e/tests/backend/endpoints/api/v1/internal/mcp.test.ts` — **6/6 pass** (verifies the new `ask_hexclave` tool — the hand-written inline snapshot matched actual MCP server output). - `pnpm test run apps/e2e/tests/backend/endpoints/api/v1/internal/projects.test.ts` — **11/11 pass** (verifies wire dual-accept + dual-emit end-to-end; the snapshot serializer fix was found and applied during this check). A four-agent parallel **review pass** also audited the full diff for logic/runtime bugs across the work-areas (wire headers + JWT, cookies + bearer + symbols, env vars, query params + config + MCP + aliases). All in-slice review verdicts were ✓ except the three bugs listed above, which are now fixed. ## Known follow-ups (out of scope for this PR) - **E2E snapshots across the rest of the suite** — backend now dual-emits `x-hexclave-{known-error,actual-status}` alongside `x-stack-*`, which legitimately appears in inline snapshots throughout `apps/e2e`. Two were regenerated here as a sample; the rest should regen with `vitest -u` in CI. - **Docker shell env vars beyond `PORT_PREFIX`** — `entrypoint.sh` still reads `STACK_*` env vars directly (the JS-side `getEnvVariable` transform doesn't help the shell). JS consumers dual-read so it works in practice; full shell-level dual-read is a deeper self-host follow-up. - **`@stackframe/stack-cli` build ordering** — pre-existing; needs `build:rde-standalone` first. Not affected by this PR. ## Test plan - [ ] CI runs full e2e suite (with `vitest -u` to absorb dual-emit snapshot deltas, then committed back) - [ ] Spot-check: an old SDK build (emitting only `x-stack-*`) still authenticates against the new backend - [ ] Spot-check: a new SDK (emitting `x-hexclave-*` / `Bearer hexclave_*`) still authenticates against an old backend during deploy ordering - [ ] Manual: `npx @stackframe/stack-cli@latest init` (new onboarding entrypoint) generates `hexclave.config.ts` - [ ] Manual: existing `stack.config.ts`-only project still resolves (no migration required) --------- Co-authored-by: bilal <[email protected]>	2026-05-23 17:24:55 -07:00
4 people	2055d98dea	External db sync (#1036) ... <img width="1920" height="969" alt="Screenshot 2026-02-04 at 9 47 16 AM" src="https://github.com/user-attachments/assets/d7d0cd04-0051-4fc4-b857-e6f87ee97a59" /> **This PR revolves around the following components** 1. Sequencer - sequences the updates in the internal db 2. Poller - polls for the latest updates to sync with the external db 3. Outgoing Request Handler - essentially a trigger that can make http requests based on a change in the internal db 4. Sync Engine - syncs with the latest changes from the internal db to the external db **What has been done** - Added a global sequence id for ProjectUser, ContactChannel and DeletedRow. - Added the deletedRow table to keep track of the rows that were deleted across ProjectUser and ContactChannel. - Added the OutgoingRequest table to keep track of the outgoing requests - Added function for the sequencer to call to sequence updates - Added a sequencer that sequences all the changes in the internal db every 50 ms - Added a poller that polls for the latest changes in the internal db every 50 ms, and adds to a queue - Added a Vercel cron that calls sequencer and poller every minute - Added a queue that fulfills the outgoing requests by making http calls (for external db sync, it calls the sync engine endpoint) - Added a sync engine that uses the defined sql mapping query in the user's schema to pull in the changes for the user, and sync them with the external db - Added tests to test out each functionality **How to review this PR:** 1. Review the migrations (sequence id, deletedRow, triggers, backlog sync) (all files created under the migrations folder) 2. Review sequencer 3. Review poller 4. Review the changes in schema 5. Review sync-engine (the function, and it's helper file) 6. Review the schema changes, and query mappings 7. Review the tests (basic, advanced and race, along with the helper file) 8. Review the changes made in Dockerfile to support local testing using the postgres docker <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Introduces a cron-driven external DB sync pipeline with global sequencing, internal poller and webhook sync engine, new DB tables/functions, config schema/mappings, and comprehensive e2e tests. > > - **Database (Prisma/Migrations)**: > - Add global sequence (`global_seq_id`) and `sequenceId`/`shouldUpdateSequenceId` to `ProjectUser`, `ContactChannel`, `DeletedRow` with partial indexes. > - Create `DeletedRow` (capture deletes) and `OutgoingRequest` (queue) tables; add unique/indexes. > - Add triggers/functions: `log_deleted_row`, `reset_sequence_id_on_update`, `backfill_null_sequence_ids`, `enqueue_tenant_sync`. > - **Backend/API**: > - New internal routes: `GET /api/latest/internal/external-db-sync/sequencer`, `GET /poller`, `POST /sync-engine` (Upstash-verified) for sync orchestration. > - Add cron wiring: `vercel.json` schedules and local `scripts/run-cron-jobs.ts`; start in dev via `dev` script. > - Tweak route handler (remove noisy logging) without behavior change. > - **Sync Engine**: > - Implement `src/lib/external-db-sync.ts` to read tenant mappings and upsert to external Postgres (schema bootstrap, param checks, sequencing). > - Add default mappings `DEFAULT_DB_SYNC_MAPPINGS` and config schema `dbSync.externalDatabases` in shared config. > - **Testing/Infra**: > - Add extensive e2e tests (basics, advanced, race conditions) for sequencing, idempotency, deletes, pagination, multi-mapping, and permissions. > - Docker compose: add `external-db-test` Postgres for tests; e2e deps for `pg` types. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 3f2a8efcfb. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * External PostgreSQL sync: automatic, batched replication with mappings, resume/idempotency, and on-demand enqueueing. * **Admin UI** * Real-time External DB Sync dashboard and status API showing per-mapping backlog, sequencer/poller/sync-engine telemetry, and fusebox controls. * **Tests** * Large e2e suite: basic, advanced, race, high-volume tests and test utilities for external DB sync. * **Chores** * DB migrations, CI/workflow updates, background cron runner and local/dev test support. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Konsti Wohlwend <[email protected]> Co-authored-by: Bilal Godil <[email protected]>	2026-02-05 12:04:31 -08:00
Konstantin Wohlwend	cf86ea5952	Proxy caching	2026-02-05 11:30:40 -08:00
Konstantin Wohlwend	8514363ae7	Fix dev stats accuracy	2025-12-29 17:15:08 +01:00
Konstantin Wohlwend	af2436ec13	Dev stats view	2025-12-29 17:06:40 +01:00
Konstantin Wohlwend	9c9a370d47	Upgrade backend to Next.js 16	2025-12-12 16:59:07 -08:00