fix: fix assigning the readonly require on global object #29
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.
As the runtimes set the require as a readonly property to global object, it is not possible to assign to it when "strict" mode is used.
The following code throws an error in runtime
TypeError: Attempted to assign to readonly property.
Currently when
tsc
is used, the produced code is instrict
mode and it does not work in runtime.Currently when
grunt
is used, the produced code is not instrict
mode.The new behavior unifies the
tsc
andgrunt
commands and compiles the code in nonstrict
mode.