Skip to content

chore(eve): keep unsigned JWT fixture out of package builds - #1739

Draft
vercel-gh-bot-5[bot] wants to merge 1 commit into
mainfrom
e0/c573954c-6383-49a9-82ca-441837e417e0
Draft

chore(eve): keep unsigned JWT fixture out of package builds#1739
vercel-gh-bot-5[bot] wants to merge 1 commit into
mainfrom
e0/c573954c-6383-49a9-82ca-441837e417e0

Conversation

@vercel-gh-bot-5

Copy link
Copy Markdown

On main, pnpm --filter eve run clean && pnpm --filter eve run build:types emits dist/src/public/models/openai/chatgpt/unsigned-jwt.d.ts at 228 bytes. Repository search shows createUnsignedJwt has three consumers, all in tests.

The hypothesis is that moving this fixture to the existing src/internal/testing boundary will preserve test behavior and exclude test-only code through the existing tsconfig.build.json rule.

before: ChatGPT tests -> public/models/.../unsigned-jwt.ts -> package declarations
after:  ChatGPT tests -> internal/testing/unsigned-jwt.ts -> excluded from package build

A clean full package build now emits no file matching *unsigned-jwt*.

Validation:

  • pnpm --filter eve exec vitest run --config vitest.unit.config.ts --maxWorkers=4 (6,024 passed, 1 skipped)
  • pnpm --filter eve typecheck
  • pnpm --filter eve run build
  • pnpm guard:invariants
  • pnpm exec oxlint <changed files> --report-unused-disable-directives
  • pnpm exec oxfmt --check <changed files>

@vercel

vercel Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
eve-docs Ready Ready Preview Aug 6, 2026 8:07pm
eve-docs-4759 Ready Ready Preview, v0 Aug 6, 2026 8:07pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants