Skip to content

fix(browser-tests): scope NODE_ENV per server in CI - #91

Merged
VladUZH merged 1 commit into
mainfrom
fix/browser-ci-env-scoping
Jul 29, 2026
Merged

fix(browser-tests): scope NODE_ENV per server in CI#91
VladUZH merged 1 commit into
mainfrom
fix/browser-ci-env-scoping

Conversation

@VladUZH

@VladUZH VladUZH commented Jul 29, 2026

Copy link
Copy Markdown
Member

Root cause #7, a collision between two earlier fixes: the job-wide NODE_ENV=development (#87, needed for the API's dev auth bypass) poisons next build (#90's production servers) — prerender runs with the dev React runtime and fails on /404 with the misleading <Html> should not be imported outside pages/_document error (run 30464116024).

Fix: the two Next apps build and serve under an explicit NODE_ENV=production inside their webServer commands; the API keeps inheriting development. Will chain validation #7 after merge.

🤖 Generated with Claude Code

…uilds

The CI job exports NODE_ENV=development for the API's dev auth bypass
(#87), which poisons 'next build': prerender runs with the dev React
runtime and fails on /404 with the misleading '<Html> imported outside
_document' error. The two Next apps now build and serve with an
explicit NODE_ENV=production; the API inherits development as intended.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@VladUZH
VladUZH merged commit ff0042c into main Jul 29, 2026
19 checks passed
@VladUZH
VladUZH deleted the fix/browser-ci-env-scoping branch July 29, 2026 15:18
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