feat: introduce RunnableDevEnvironment #18190
Draft
+125
−54
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
This PR introduces a new concept to the Environment API - the
RunnableDevEnvironment
. This is the environment that has a module runner in the same process. You can access it directly asenvironment.runner
. The runner itself is evaluated eagerly when it's accessed for the first time.By default, Vite SSR dev environment is a runnable environment. Due to environments being available during the build, there are some constraints in typing. You can either cast it to
RunnableDevEnvironment
or type guard it withisRunnableDevEnvironment
.You can create your own runnable environments using the
createRunnableDevEnvironment
function:You can configure the runner with the
runner
option (the previousrunner
option was renamed toremoteRunner
):