chore: use real VITEST_API_TOKEN for ui dev#10279
Merged
sheremet-va merged 21 commits intovitest-dev:mainfrom May 7, 2026
Merged
chore: use real VITEST_API_TOKEN for ui dev#10279sheremet-va merged 21 commits intovitest-dev:mainfrom
VITEST_API_TOKEN for ui dev#10279sheremet-va merged 21 commits intovitest-dev:mainfrom
Conversation
✅ Deploy Preview for vitest-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
hi-ogawa
changed the title
VITEST_API_TOKEN for ui dev
Remove the build-time UI token escape hatch and stale CI/test wiring now that local UI dev injects the real token from the Vitest UI server. Co-authored-by: Codex <noreply@openai.com>
Fetch the browser runner HTML from the active browser dev server and inject its generated runner state into the UI dev page instead of relying on the manual browser.dev.js stub. Co-authored-by: Codex <noreply@openai.com>
Use shorter BROWSER_DEV and BROWSER_DEV_PORT names for the UI browser preview workflow. Co-authored-by: Codex <noreply@openai.com>
Document that the default UI dev workflow points at the test/unit API port and explain how to align custom backend ports. Co-authored-by: Codex <noreply@openai.com>
Use explicit error checks when fetching and extracting development UI scripts. Co-authored-by: Codex <noreply@openai.com>
sheremet-va
requested changes
May 7, 2026
sheremet-va
approved these changes
May 7, 2026
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
2 participants
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.
Description
Mostly reverting #8044 but instead of hard-coding
VITEST_API_TOKEN = 0, this now extracts and inject real token from real test server. The same extraction mechanism is used for__vitest_browser_runner__on browser orchestrator UI too.See updated
packages/ui/CONTRIBUTING.mdfor the guide.For the reason to prefer real token, I think this was a bug which got missed out because of 0 token.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yamlunless you introduce a new test example.Tests
pnpm test:ci.Documentation
pnpm run docscommand.Changesets
feat:,fix:,perf:,docs:, orchore:.