Repository navigation
Conversation
Deploying fliplet-cli with
|
| Latest commit: |
879be59
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e1cb9d40.fliplet-cli.pages.dev |
| Branch Preview URL: | https://codex-vue-runtime-docs-fix.fliplet-cli.pages.dev |
This branch has not been 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.
Vue guidance currently contradicts the built-in runtime loader, causing workers to request an unnecessary SFC dependency. This change documents
parseSFCandevalModule, preserves the unsupported compiler features, and aligns the routing example with guarded manifest-based navigation so denied or failed requests are not evaluated as source.Reuses the relevant correction from #315 on current master, with navigation guards and executable regression coverage added. It is separate from the Studio harness changes and is intended for a non-production docs preview during matched build tests; production publication remains separate.
Validation: 230 documentation tests passed; the two recipe tests also passed against the paired API's actual media/router implementations and real Vue/Vue Router. Strict index generation, Jekyll build and Markdown sibling generation passed. Existing unrelated Jekyll warnings and the pre-existing dompurify advisory are unchanged.