Import path autocomplete regression: No classic resolution autocomplete when package does not have any "exports" but resolves fine

[itsUndefined]

🔎 Search Terms

"resolvePackageJsonExports", "no file autocomplete when importing internal package files with moduleResolution node16"

🕗 Version & Regression Information

This changed between versions 5.7.0-dev.20241031 and 5.7.0-dev.20241101

Confirmed the issue exists on typescript@next

⏯ Playground Link

https://codesandbox.io/p/devbox/qpxkh5?file=%2Findex.ts%3A13%2C1

💻 Code

// This resolves correctly but it doesn't autocomplete the /internal path even
// though the package @my/base (inside the folder base-package) does NOT have "exports" inside the package.json
import { INTERNAL_CONSTANT } from "@my/base/internal";

// try to update the import below to include the "/internal" at the end and see that it does not autocomplete

import { INTERNAL_CONSTANT as INTERNAL_CONSTANT2 } from "@my/base";

// try to set resolvePackageJsonExports to false inside tsconfig.json and try to update the import above again. 
// Autocomplete works AS EXPECTED.

🙁 Actual behavior

Autocomplete of internal folders of packages without "exports" does not work when "resolvePackageJsonExports": true

🙂 Expected behavior

Autocomplete of internal folders of packages without "exports" inside the package.json should be the same whether the resolvePackageJsonExports flag is enabled or not

Additional information about the issue

Regression must have happened between 10/31/2024 and 11/1/2024 based on my testing of the nightly builds. Could not provide a non-VM sandbox of the issue because it requires 2 npm packages to show the issue ( monorepo style )