Repository navigation
package self-reference works without a flag in node v12.16 #31754
Description
Activity
This is definitely a bug, unfortunately due to the nature of the backporting process between the flagged and unflagged implementations. The fix would be to include an explicit
if (!experimentalModules) returnin the first line of thetrySelffunction in lib/internal/modules/cjs/loader.js for the 12.x branch.Reacted by Jordan Harbandwe can get out an emergency release to fix this
Reacted by Jordan Harband, Quinn Chaffee, Ernst Ammann and Michael ChambaudReacted by Jordan Harband, Quinn Chaffee and Michael Chambaud
Repro: clone https://github.com/ljharb/has-package-exports
It has a dev dep of
"has-package-exports": "file:.", so that in every node version, i canrequire('has-package-exports')from within the package, and it works.In node v13.6 and v12.15,
node testpasses without issuing(node:96292) ExperimentalWarning: Package name self resolution is an experimental feature. This feature could change at any timeas a warning.In node v13.7, the warning is correctly issued, and the local dev dep is byassed.
However, in node v12.16, without passing any flags, the warning is issued and the local dev dep is bypassed. v12.16 and v12.15 should behave identically with respect to this feature, regardless of the presence of "exports" in package.json.
cc @nodejs/modules-active-members