fix: duplicate init typescriptLoader #641
Closed
Conversation
This file contains hidden or 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
|
|
alexander-akait
approved these changes
Apr 4, 2023
Member
alexander-akait
left a comment
There was a problem hiding this comment.
Oh, good catch, souds like node-ts has memory leak...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR contains a:
Motivation / Use-Case
Breaking Changes
Additional Info
Each time the
typescriptLoaderis executed, ts-node will executeregisterExtension()once.Multiple executions of the
typescriptLoaderwill getrequire.extensions[ext] = wrapper(wrapper(wrapper(wrapper(wrapper(... wrapper(originalHandler))))).ts-node source code
This will cause the out of memory when
require.extensions[ext]is executed. #638