Repository navigation
Fix Windows env filtering and React test output stalls - #376
Merged
Merged
Conversation
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://fix-windows-env-ci-void-cloud.voidzero-docs.workers.dev (commit 30d6b3d)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
This branch was successfully deployed
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.
Windows CI can compare a short or differently cased project path with Vite's canonical
envDirand treat the same directory as a separate dotenv source. This lets local.envvalues enter production client builds. Use the native realpath resolver for both paths and add a real-build regression for a differently cased directory alias.Also drain the React dev test server's stdout and stderr with the existing diagnostics helper. Unread stdout can fill its pipe and stall the server; startup failures now include bounded output and detect an exited process.
Validation: local full-suite coverage passed 13,028 tests, including platform reruns after generating the clean worktree's dashboard types. The env integration file passes all 39 tests and the React client file passes all 43. Typechecking, lint, and npm/pnpm packed smoke checks pass. Linux and Windows CI are green, including both Windows integration shards, unit tests, builds, and typechecking.