Repository navigation
Fix Nuxt cold-start runtime identity and verify native replay - #78
Merged
Merged
Conversation
|
View your CI Pipeline Execution ↗ for commit 0e7a87a
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
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.
On a cold Nuxt 3 start, the native plugin could initialize a raw ESM RuntimeManager while application queries imported a separate Vite-prebundled copy. The page and overlay rendered, but the queried runtime never became ready. Exclude the runtime from prebundling, preserving existing excludes, so both paths share the initialized adapter.
Extend portable replay regression coverage to native Next App Router (15/Webpack and 16/Turbopack) and Nuxt SSR (3/4). Add these four cases to existing CI, alongside React/Vue Vite cases. Check live committed state, stale handles after unmount, fresh-session replay and correct UI updates, console/page/network errors, and conditional production instrumentation removal. Build/server process groups now have bounded cleanup with retained failure logs.
Validation:
These are local-artifact installs; pnpm explicitly overrides Domscribe dependencies to those tarballs. This is not a published-package release or full router/version matrix. The APIs remain limited to main-document light DOM and explicit replay steps. No publication, deployment, settings changes or issue-to-PR GitHub Action product is included.