feat(runtime): add startOn environment option #1516
Draft
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.
π Linked issue
resolves #1496
β Type of change
π Description
I explored whether we could mock the modules used in our global middleware using the existing setupFile mechanism that starts the NuxtApp. However, I realized that this approach couldn't support both scenarios: mocking the module when the NuxtApp starts and mocking it after it has already started.
To resolve this, I introduced a new startOn option. This allows us to choose the timing for starting the NuxtApp, which can now be toggled per test file using @vitest-environment-options.