denoland-deno/tests/registry/npm/@denotest/cjs-multiple-exports/1.0.0/package.json

{
  "name": "@denotest/cjs-multiple-exports",
  "version": "1.0.0",
  "exports": {
    ".": "./src/index.js",
    "./add": "./src/add.js"
  }
}
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-10-31 13:02:31 -04:00			`{`
			`"name": "@denotest/cjs-multiple-exports",`
			`"version": "1.0.0",`
			`"exports": {`
			`".": "./src/index.js",`
			`"./add": "./src/add.js"`
			`}`
			`}`