unable to resolve packages with a nested package.json

[thescientist13]

Type of Change

Bug

Summary

Found a case out in the wild where a package, in this case luxon has a nested package.json in its src/ folder, thus when we recursively walk up from the location returned from import.meta.resolve, we hit this false positive and thus exit the search too early.
https://github.com/thescientist13/import-meta-resolve-luxon?tab=readme-ov-file#demo

• What we want - file:///Users/path/to/.../node_modules/luxon/
• What we got - file:///Users/path/to/.../node_modules/luxon/src/

And so in development and building up the import map, we'll get this diagnostic from Greenwood
thescientist13/HP_Stuff#1 (comment)

WARNING: No supported entry point detected for => `luxon`
Learn more about these warnings at => https://greenwoodjs.dev/docs/introduction/web-standards/#import-maps

Details

So seems we need to add some additional heuristics which might now require actually having to read the entire contents of package.json though :/

for (const segment of segments.slice(1)) {
  if (fs.existsSync(new URL('./package.json', root))) {
    const resolvedPackageJson = (await import(new URL('./package.json', root), { with: { type: 'json' } })).default;
    const { name, version, main, module, exports } = resolvedPackageJson;

    // name and version are required fields in a package.json_
    // https://docs.npmjs.com/cli/v10/configuring-npm/package-json
    if ((name && version) && (main || module || exports)) {
      break;
    }
  }

  root = root.replace(`${segment}/`, '');
}