nodenext moduleResolution can't resolve package types correctly

[tjx666]

Bug Report

🔎 Search Terms

nodenext, moduleResolution, exports

🕗 Version & Regression Information

happen on typescript@5.0 to typescript@next

⏯ Playground Link

Playground link with relevant code

The playground seems can't save my tsconfig.
You need to set:

• target: ESNext
• module: nodenext

💻 Code

import vitePluginVue2 from '@vitejs/plugin-vue2';

console.log(vitePluginVue2());

🙁 Actual behavior

This expression is not callable.
  Type 'typeof import("file:///node_modules/@vitejs/plugin-vue2/dist/index")' has no call signatures.(2349)

🙂 Expected behavior

No compile error

[RyanCavanaugh]

I don't think nodenext module resolution is just uniformly broken -- much more likely this is a misconfigured package. Can you be more specific about why you think this is a wrong result, and include a sample repo to demonstrate?

[RyanCavanaugh]

Looks like this is just how vitejs has decided to ship their code. See vitejs/vite-plugin-react#104 and specifically vitejs/vite-plugin-react#104 (comment) / vitejs/vite-plugin-react#104 (comment)

[tjx666]

I just want to to know why tsc throw this error when I using moduleResolution：nodenext. The package had already configured the types using package.json exports and the .d.ts is also exits.

Can you be more specific about why you think this is a wrong result, and include a sample repo to demonstrate?

Why not click the playground link.

[RyanCavanaugh]

We'll have some new module docs soon that will explain all of this in more detail.

[sircumferencee]

@RyanCavanaugh How soon? This all is just extremely confusing

[RyanCavanaugh]

@MrHBS probably a preview version available in a couple weeks

[RyanCavanaugh]

@MrHBS see #52593 (comment)