Can not resolve when package.json exports field resolution result is a direcory

Describe the bug

I have a package named some-package and it’s files are in node_modules.

package.json in node_modules/some-package

{
  "name": "some-package",
  "version": "1.0.0",
  "license": "MIT",
  "exports": {
    ".": "./index.js",
    "./sub": "./lib/sub"
  }
}

index.js in node_modules/some-packages/lib/sub

export const Foo = 'Foo';

then I import it in the main.js in root directory

import { Foo } from 'some-package/sub';
console.log(Foo);

it complain the error

I also run the same code in Node.js or Webpack-based project, they can correctly resolve some-package/sub

In previous issue #7267 I know how to fix it. I’m willing to submit a PR with well-tested code❤️ if Vite team think it’s a bug

Reproduction

https://stackblitz.com/edit/vitejs-vite-cz6tvn?file=main.js

System Info

I don't know the system info in Stackbliz. But this issue is not platform-related I think

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it’s a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

Do not rely on this flag. We plan to remove it once the Loaders API has advanced to the point that equivalent functionality can be achieved via custom loaders. https://nodejs.org/api/esm.html#customizing-esm-specifier-resolution-algorithm

It seems --experimental-specifier-resolution=node is planed to be removed in future. It might be better to think of supporting custom loaders rather than this flag specifically.

IMHO relying on a flag / custom loader is not good for packages.

[3lang3]

some issue.

nextjs remix wepack(cra, umi) resolve success.

only vite throw err