Repository navigation
Fix React and Vue starter startup in StackBlitz - #52
Merged
Merged
Conversation
1 task done
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.
Opening the React starter in StackBlitz failed before Vite started: Rolldown's fallback installed dependencies outside the project lockfile and selected a WASM runtime with incompatible peers. Both React and Vue starters now explicitly include the matching WASM binding and pin its compatible runtime, so the project lockfile controls startup. Their Node requirements and setup notes reflect the dependency requirements.
Fullbleed stays at 0.8.2 / engine 2.5.37; application code and document templates are unchanged.
Validation: both exact-lock installations and production builds passed. Existing Chrome download checks and React Vite source-edit checks passed, with all existing PDFs unchanged. Fresh anonymous StackBlitz projects produced six PDFs after data, template/component, and stylesheet edits. Fixture hashes and scoped results are retained in
verification/stackblitz-startup-20261026.json; the existing CI browser matrix remains required before merge.