mirror of
https://github.com/stack-auth/stack.git
synced 2026-06-30 21:01:54 +08:00
7539fb9fbf
The env-var rename added conflict-detecting dual-read (HEXCLAVE_* wins over STACK_*, throws when both differ) and set HEXCLAVE_* to non-empty values in the checked-in .env.development files. Tests that stubbed the legacy STACK_* twin either triggered the conflict throw or were silently shadowed by the canonical HEXCLAVE_* value loaded from .env. Point the test env stubs at the canonical HEXCLAVE_* names (production reads keep the legacy STACK_* argument and rely on dual-read): - plan-entitlements.test.ts: HEXCLAVE_DISABLE_PLAN_LIMITS - turnstile.tsx / users.tsx: HEXCLAVE_DISABLE_BOT_CHALLENGE, HEXCLAVE_ALLOW_SIGN_UP_ON_VISIBLE_BOT_CHALLENGE_FAILURE - access-token-helpers.tsx: HEXCLAVE_ALLOW_SHARED_OAUTH_ACCESS_TOKENS - url-targets.test.ts: NEXT_PUBLIC_HEXCLAVE_HOSTED_HANDLER_* Also fix the turnstile dev-secret-key test to clear both twins so it actually exercises the dev-key fallback instead of passing on a string coincidence. |
||
|---|---|---|
| .. | ||
| prisma | ||
| scripts | ||
| src | ||
| .env | ||
| .env.development | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| instrumentation-client.ts | ||
| LICENSE | ||
| next.config.mjs | ||
| package.json | ||
| prisma.config.ts | ||
| tsconfig.json | ||
| vercel.json | ||
| vitest.config.ts | ||
| vitest.setup.ts | ||