feat: support concurrent browser async context#39
Draft
kasperpeulen wants to merge 7 commits into
Draft
Conversation
commit: |
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
.run()calls instead ofenterWithunctxin the Next playgrounds so browser-mode CI does not reload tests mid-importValidation
pnpm --dir packages/vitest-plugin-rsc exec vitest run src/async-local-storage.test.ts src/async-local-storage-transform.test.tspnpm --dir packages/vitest-plugin-rsc run buildpnpm tsgo --buildpnpm format:checkpnpm lintVITEST_BROWSER_API_PORT=64123 pnpm --dir playground/rsc-vitest-demo exec vitest runVITEST_BROWSER_API_PORT=64124 pnpm --dir playground/nextjs-notes-demo exec vitest runVITEST_BROWSER_API_PORT=64125 pnpm --dir playground/nextjs-no-msw-demo exec vitest run