fix(astro-agent-markdown): exclude yaml from dev optimizer#275
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
onequery-landing | 8274aeb | Commit Preview URL Branch Preview URL |
Jun 04 2026, 08:01 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One-Line Summary
Prevent Astro dev from hitting a Vite SSR optimizer reload crash after the agent Markdown middleware loads YAML.
User-Facing Changes
yamlout of the server-side Vite dep optimizer for@onequery/astro-agent-markdowndev middleware..vite/deps_ssr/chunk-*.jsfile after optimized dependencies reload.Why This Changed
PR #274 added build-time agent Markdown bundles and attempted to pre-optimize
yamlduring dev SSR. In the Cloudflare dev runner, that can cause Vite to rewrite the SSR optimized dependency cache during a full reload while workerd is still resolving the previous chunk path.The result is a local dev crash like:
The file does not exist at ".../node_modules/.vite/deps_ssr/chunk-*.js" which is in the optimize deps directory.How It Changed
optimizeDeps.includetooptimizeDeps.excludeforyaml.Bug Fixes
astro devwith the Cloudflare adapter, loading the agent Markdown middleware could trigger a full reload afteryamloptimization and leave the worker resolving a staledeps_ssrchunk. This change keepsyamlas source in server environments to avoid that optimizer invalidation path.Extra Context / Decisions (Optional)
The generated agent Markdown bundle behavior from PR #274 is unchanged. This only adjusts dev-server dependency handling.
Verification
rtk git merge origin/mainrtk mise exec -- bun run formatrtk mise exec -- bunx turbo test --json --filter=@onequery/astro-agent-markdownrtk mise exec -- bunx turbo typecheck --json --filter=@onequery/astro-agent-markdownturbo lintwith type-aware lint completed with 0 warnings and 0 errors.Dev-server smoke validation was not completed in this pass after the workflow was redirected to merge/push/PR.
Video / Screenshot (Optional)