fix(build): trace YAML spec dirs so Vercel ships latest dev specs - #634
Merged
Conversation
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
1 participant
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.
Add outputFileTracingIncludes to next.config.ts so the file tracer picks up YAML files outside src on every Vercel build. Specs in benchmarks, answers, alternatives are read at runtime via fs.readFile relative to process.cwd. Without this hint Next's default tracer only follows static imports so those YAML files were not making it into the prebuilt deployment artifact and the deployed page kept serving an old snapshot of pm-api-latency.yml that missed PR 606 (Mobula, Predexon, Codex aggregator providers + source=direct selectors). After this fix every deploy ships the dev HEAD of each spec.