Add testing harness that replicates FastBoot environment. #19123
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.
Prior to this we were simulating FastBoot in a non-isolated VM context. That meant that the running Node context was available within rendering attempts. However, when ran with "real" FastBoot that is not the case. In the real FastBoot environment, we create an isolated
vm
context and evaluate both Ember and the application within that context. This ensures that the running context does not have access to arbitrary Node-land APIs (e.g.require
).This replicates the failure that is reported in glimmerjs/glimmer-vm#1141: