Conversation
|
3 tasks done
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.
Rollup Plugin Name:
{name}This PR contains:
Are tests included?
Breaking Changes?
Description
On Node 23+,
requireReturnsDefault: 'auto'hands bundled CommonJS code a namespace object where plain Node would returnmodule.exports.The runtime helper
getDefaultExportFromNamespaceIfNotNamedunwraps a required external module only whendefaultis the sole key on its namespace. Since nodejs/node#53848 (Node 23), a CommonJS namespace always carries a second key,'module.exports':
js Object.keys(await import('mquery')); // Node 22: ['default'] // Node 23+: ['default', 'module.exports'] So the check never passes, the requiring code receives the namespace, and calls like
new mquery()throwmquery is not a constructor. Nuxt and SolidStart apps hit this through Nitro, which bundles database drivers while keeping the drivers' dependencies external (see getsentry/sentry-javascript#24775 for a full analysis).The fix: when the namespace has a
'module.exports'key, return its value. Node puts the realmodule.exportsbehind that key, so this is exactly whatrequire()would return, with no guessing. Namespaces without the key keep the current behavior, so nothing changes on Node 22 or for genuine ES modules.