build: Add node export for better compatibility
#6716
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.
Background
On Next.js, we noticed that instrumentation via
import-in-the-middleof this package was not working. After some deep debugging, I figured out that the problem seems to be that it keeps picking up the.mjsvariant in Next.js, although Next itself is cjs. That seems to mess with import-in-the-middle (or actually require-in-the-middle, I suppose).The only way to fix this and get it to load the cjs correctly in Next.js was to add a
nodevariant export.Summary
Added a
nodevariant export that points to the cjs outout.