fix: make StackBlitz startup WebContainer-safe - #19
Merged
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
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.
Summary
.stackblitzrcand every GitHub/Pages live-lab link atdev:stackblitzpnpm checkso the path remains release-gatedUnreleasedwithout moving or rewritingv1.0.0-beta.2Reproduction
The deployed live-lab link imported the repository, then failed in StackBlitz WebContainers at
turbo run buildwithreached EOF without closing quotefrom the native Turbo binary.Validation
packages/*/distaway, thenpnpm build:stackblitzrebuilt all nine packages successfully in dependency orderpnpm dev:stackblitzreached a ready Vite 8 development server locallyCAUSESCOPE_DOCS_BASE=/causescope/ pnpm docs:builddev:stackblitzscriptAfter merge