`typesVersions` doesn't match behaviour of `exports`

🔎 Search Terms

• "typesVersions"
• "exports"

🕗 Version & Regression Information

• This relates to the work around Node.js exports (i.e. #53116).
• This has never worked to my knowledge.

⏯ Playground Link

No response

💻 Code

package.json:

{
  "exports": {
    "./*": {
      "types": "./dist/types/*/*.d.ts",
      "import": "./dist/esm/*/*.js",
      "require": "./dist/cjs/*/*.js"
    }
  },
  "typesVersions": {
    "*": {
      "*": [
        "./dist/types/*/*.d.ts"
      ]
    }
  }
}

🙁 Actual behavior

These provided export paths work as expected in Node.js. For example, I can import from foo/dist/esm/bar/bar.js with:

import { bar } from 'foo/bar';

However, TypeScript is unable to resolve the double wildcard in typesVersions. I also see a validation error on the string ("./dist/types/*/*.d.ts") in VS Code.

🙂 Expected behavior

I'd expect that typesVersions behaves the same way that exports does.

Additional information about the issue

I realise that a quick solution to this would be to use index.js in each folder instead of a file with the same name as the folder, but wanted to report the different in behaviour here.

This may also technically be a feature request.

Start with the package.json example and reproduce resolution of the double wildcard in typesVersions against the corresponding exports pattern. Then trace TypeScript's module-resolution handling for these fields and its validation path. Done means the documented pattern is accepted and resolves consistently with the exports behavior.