Nathan Whitaker 68cee70838 fix(ext/node): resolve exports even if parent module filename isn't present (#26553) ... Fixes https://github.com/denoland/deno/issues/26505 I'm not exactly sure how this case comes about (I tried to write tests for it but couldn't manage to reproduce it), but what happens is the parent filename ends up null, and we bail out of resolving the specifier in package exports. I've checked, and in node the parent filename is also null (so that's not a bug on our part), but node continues to resolve even in that case. So this PR should match node's behavior more closely than we currently do.		2024-11-06 00:36:23 +01:00
..
jsr	fix(install): cache json exports of JSR packages (#26552)	2024-10-30 00:15:37 +01:00
npm	fix(ext/node): resolve exports even if parent module filename isn't present (#26553)	2024-11-06 00:36:23 +01:00
npm-private/@denotest	fix(npm): use configured auth for tarball urls instead of scope auth (#24111)	2024-06-05 21:24:52 +00:00
npm-private2	fix(npm): use configured auth for tarball urls instead of scope auth (#24111)	2024-06-05 21:24:52 +00:00
npm-private3/@denotest3/basic/1.0.0	fix: .npmrc settings not being passed to install/add command (#26473)	2024-10-25 02:09:38 +02:00