babel-register run default register with global module cache #12674
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.
Small follow-up to PR #12665.
This moves the default call to
register()
fromnode.js
intonodeWrapper.js
, soregister()
executes with global module cache.In my original implementation, the default call to
register()
executes with internal module cache, whereas the user callingregister( /* options */ )
executes with global module cache.Right now, it makes no difference either way, as
register
function contains no code which could callrequire()
. But if this changed in future, this amendment would ensure behaviour is consistent.Sorry, I should have included this in the previous PR.