fix(browser-tests): production Next builds in CI, dev servers locally - #90
Merged
Conversation
Validation run #5: 75 passed, 35 failed — every failure a selector or fill timeout concentrated on first-visit pages (landing 16, signup 16), none reproducible locally. Dev-mode Next compiles each page on first hit; a 2-core CI runner takes >30s per cold page. CI now builds and serves production bundles (compile cost paid once, up front, inside a 7-minute webServer timeout); local runs keep dev servers. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Validation #5 (run 30460483491): 75 passed / 35 failed, and every failure is a first-visit timeout (landing ×16, signup ×16, …) that never reproduces locally. Classic dev-server-in-CI failure: Next dev compiles pages on first hit and a 2-core runner takes >30s per cold page.
CI now runs
next build && next startfor dashboard and landing (compile paid once inside a 7-min webServer timeout); local runs keep dev servers unchanged. The API stays on its dev server everywhere — tsx has no per-page compile.Sixth and, evidence suggests, final root cause: 1 missing server → 2 env parity → 3 seed scope drift → 4 stale enum vocab → 5 unscoped locator → 6 dev-server cold compiles. Will dispatch validation #6 after merge.
🤖 Generated with Claude Code