stack/examples
Bilal Godil c59643855d fix(hexclave): address second-wave reviewer findings (PR 3 scope)
Three small fixes from the parallel reviewers on PR 3:

1. **tanstack-start-demo vite SSR regex** — examples/tanstack-start-demo/
   vite.config.ts:76 had `noExternal: [/^@stackframe\//, ...]`. The
   regex was missed by the source rename sweep because it's a regex
   pattern, not a string literal. After the rename no @stackframe/*
   package exists in the workspace, so the regex matched nothing and
   workspace deps (`@hexclave/tanstack-start`, `@hexclave/shared`,
   `@hexclave/ui`) stopped being inlined for SSR. Without inlining,
   the Nitro server hits ERR_REQUIRE_ESM on first request because the
   CJS bundles import ESM-only transitive deps (jose, oauth4webapi).
   Flipped to /^@hexclave\// to match the renamed packages.

2. **docs.json footer GitHub link** — pointed at hexclave/stack (404,
   no such repo). The navbar at line 34 already uses hexclave/hexclave
   per the plan, so aligned the footer to match.

3. **README cleanups**:
   - Alt text 'Stack Logo' → 'Hexclave Logo' on the header image.
   - Removed broken /docs/next prefix on the setup-guide link (the
     actual docs structure is /getting-started/setup, no /docs/next).
   - contrib.rocks image now points at hexclave/hexclave (was the old
     stack-auth/stack URL).

What I did NOT touch (out of PR 3 scope, surfaced separately for a
follow-up doc-pedagogy PR):

- 14+ docs-mintlify pages teaching STACK_* env vars instead of
  HEXCLAVE_* (works via dual-read, but contradicts migration.mdx's
  'new code should use HEXCLAVE_*' recommendation).
- REST API code samples teaching X-Stack-* headers instead of
  X-Hexclave-* (works via dual-accept proxy).
- docs-mintlify/sdk/objects/stack-app.mdx broken in-page anchors
  (#stackclientapp etc. — body headings renamed in PR 2 but
  anchor IDs weren't updated).
- MCP server name inconsistency (`stack-auth` in init-prompt.ts vs
  `hexclave` in dashboard setup-page).
- The `ask_stack_auth` MCP tool was removed despite
  RENAME-TO-HEXCLAVE.md saying it should stay registered as a
  compat alias indefinitely.
- AI prompts (apps/backend/src/lib/ai/prompts.ts, apps/skills/) still
  teach legacy header / env-var names in generated code examples.

All of those are PR 2 pedagogy carry-over, not introduced by this PR,
and work functionally via the dual-read/dual-accept compat layers PR
1 + PR 2 put in place. They're documentation polish, not bugs that
block PR 3 shipping.
2026-05-23 17:41:53 -07:00
..
cjs-test feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) 2026-05-23 17:41:53 -07:00
convex feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) 2026-05-23 17:41:53 -07:00
demo feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) 2026-05-23 17:41:53 -07:00
docs-examples feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) 2026-05-23 17:41:53 -07:00
e-commerce feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) 2026-05-23 17:41:53 -07:00
js-example feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) 2026-05-23 17:41:53 -07:00
lovable-react-18-example feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) 2026-05-23 17:41:53 -07:00
middleware feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) 2026-05-23 17:41:53 -07:00
react-example fix(hexclave): address PR 3 multi-agent review findings 2026-05-23 17:41:53 -07:00
supabase feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) 2026-05-23 17:41:53 -07:00
tanstack-start-demo fix(hexclave): address second-wave reviewer findings (PR 3 scope) 2026-05-23 17:41:53 -07:00