No dynamic evaluation in /lite mode
#148
Closed
Conversation
This file contains 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.
This removes the sloppy-mode lookup for the global object from
/lite-mode, which tried to usenew Functionor indirect eval to obtainglobalThis. Instead users of/lite-mode will need to supply their own polyfill forglobalThisif the other usual suspects (global,self, or justthis) don't work. This behavior is consistent with/lite-mode's behavior of avoiding other polyfills forMap/Set/WeakMap.This does not affect the default export for
reflect-metadata.Fixes #147
Supersedes #141