Skip to content

test(astro): optimize drizzle-orm through void in the Astro playground - #594

Merged
Brooooooklyn merged 1 commit into
mainfrom
test/astro-playground-optimize-deps
Oct 26, 2026
Merged

Brooooooklyn merged 1 commit into
mainfrom
test/astro-playground-optimize-deps

Conversation

@Brooooooklyn

Copy link
Copy Markdown
Member

The Astro playground's dev smoke test (astro.test.ts > playground/astro dev) sometimes misses its 20 s start limit during a full parallel run. The server log shows why:

[WARN] Failed to resolve dependency: drizzle-orm/sqlite-core, present in ssr 'optimizeDeps.include'
astro ready
first GET / ──→ Vite finds drizzle-orm/sqlite-core now
             ──→ "optimized dependencies changed. reloading" / "program reload"
             ──→ 200 after 6.5 s  (limit already used up)

astro.config.mjs lists drizzle-orm/sqlite-core so it is optimized up front, but drizzle-orm is Void's dependency, not the playground's, so Vite can't resolve that name and skips it. This names it through Void (void > drizzle-orm/sqlite-core), the same way Void's own plugin names void > email-validator.

Fresh astro dev (.void and .wrangler removed) Warning Reload in first request First GET /
before yes yes 1.05 s on an idle machine
after none none 0.42 s

Only the playground config changes.

Seen while working on #571. vinext-pages dev failed the same way once in another run. I didn't capture its log, and its config has no optimizeDeps, so this PR doesn't claim to fix that one.

🤖 Generated with Claude Code

The playground listed drizzle-orm/sqlite-core in optimizeDeps.include, but
drizzle-orm is Void's dependency, so Vite could not resolve the name and
skipped it. The first request then found it, re-optimized and reloaded
mid-request, which made the dev smoke test miss its 20 s start limit
under a full parallel run.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-26T09:01:55.919311Z 1d79ec4 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Brooooooklyn

Copy link
Copy Markdown
Member Author

@codex review

@cloudflare-workers-and-pages

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://test-astro-playground-optimize-deps-void-cloud.voidzero-docs.workers.dev (commit 1d79ec4)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://da3b18af-void-cloud.voidzero-docs.workers.dev 1d79ec4 2026-10-26T09:01:16.317Z Visit the dashboard ↗

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 1d79ec487d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@Brooooooklyn
Brooooooklyn merged commit 0c842d5 into main Oct 26, 2026
14 checks passed
@Brooooooklyn
Brooooooklyn deleted the test/astro-playground-optimize-deps branch October 26, 2026 09:04
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.

1 participant