fix: support new ESM loader API #16
Merged
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
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 is done in a way that supports both ESM loader hook designs. It's duplicative, but luckily A) it's not much code in the first place; and B) it works 😆
IMO it's really important to support both designs right now, because while fresh
16.xinstallations (and presumably everything else going forward) will only use/need the newloadhook, alllllll previous 14 and 16 versions that people may be using use the old design.At some future point – once the API design & probably when there's a 16 LTS version – I can remove the old loader hooks and cut a new major version that raises/restricts the
enginesrequirement.Closes #13