CodeCow/stack
1
0
Fork 0
mirror of https://github.com/stack-auth/stack.git synced 2026-06-04 21:04:37 +08:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update CLAUDE-KNOWLEDGE.md: Remove outdated Q&A on template typecheck failures and clarify context provider definitions. This streamlines documentation and enhances clarity on using createGlobal for context management.

Browse Source
This commit is contained in:
mantrakp04 2026-06-02 09:54:57 -07:00
parent 13d5482cbd
commit bdeacd5d0d
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
.claude/CLAUDE-KNOWLEDGE.md
View File

@ -574,6 +574,3 @@ A: Add `docs` to `pnpm-workspace.yaml`, keep the package named `@hexclave/docs`,
## Q: How should template React contexts avoid duplicate client-bundle context identities?
A: Define exported provider contexts such as `StackContext` and `TranslationContext` through `createGlobal` from `@stackframe/stack-shared/dist/utils/globals`, not direct `React.createContext(...)` exports. That helper stores the React context under `globalThis[Symbol.for("__hexclave-globals")]`, so duplicated SDK bundles still share the same provider/consumer context object.
## Q: Why can `packages/template` typecheck fail after adding new `@hexclave/shared/dist/*` imports?
A: `packages/template` resolves `@hexclave/shared` through the shared package's generated `dist` declarations. If new shared source files or exports were merged but packages have not been rebuilt by the dev watcher, template typecheck can report missing `@hexclave/shared/dist/*` modules or members even while `packages/stack-shared` source typechecks cleanly. Do not switch back to legacy `@stackframe/stack-shared` imports to mask this; wait for or ask the user to run the package build.