feat(rsc): support non global dev runner #924
Draft
+7
−4
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
commit: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Currently we use
globalThis.__viteRscDevServer.environment.ssr.runnerto let rsc environment access ssr runner, but this assumes both rsc and ssr are runnable environments.Nitro implements server environments with runners inside a single worker, so each runner can technically communicate, but not from Vite main process. We probably need some options to switch
import.meta.viteRsc.loadModuleimplementation.Okay, nitro has
globalThis.__nitro_vite_envs__https://github.com/nitrojs/nitro/blob/a0f52cc92b0b7f5dbc7dad3f1fadb4b1d8d342e0/src/runtime/internal/vite/dev-worker.mjs#L10