Module: Support ES Modules and TypeScript, with no training wheels (moduleResolution: Node16)

[FossPrime]

Describe the feature you would like to see added

To avoid ambiguity with imports, support better tree shaking, top level async-await and compatibility problems between packages and tooling, we need to use Node16 mode in TS moduleResolution.

PrimeVue is currently very broken with direct Node16 resolution.

1. The package.json files don't define exports using standard ES Module semantics, but instead rely on the "module" property whose behavior is not standardized in NPM at the top level of package.json, only in exports.
2. The d.ts type definitions use correct default export syntax, but the ESM file uses incorrect export { PrimeVue as default, usePrimeVue } which relies on spotty and unpredictable synthetic import compatibility poly-fills... this package is running into the pitfalls of relying on that.
3. The standard, main entry point property currently points to a CJS module... which is incapable of using standard ESM default exports without webpack hacks that doesn't work on esbuild/vite/rollup.

CF: https://stackblitz.com/~/github.com/FossPrime/bug-primevue-esm-types
SBC: https://stackblitz.com/edit/public-sakai-yqyw2y?file=src%2Fmain.ts%3AL13,src%2Fvite-env.d.ts%3AL11

This is currently not a big deal as TS Support for "moduleResolution": "Node16" has some pitfalls in Vite 3.1, however there is a work being done to fix the plugins/docs, official support may come Vite 3.2/3.3.

Is your feature request related to a problem?

Describe the solution you'd like

Define exports, like the Vite plugin does https://unpkg.com/browse/@vitejs/[email protected]/package.json

And define default exports types correctly, using export default in both the type definition and the ESM code

Describe alternatives you have considered

1. Fork v3 like I did for v2
2. Write my own definitions for all components like I began to do in the sandbox.

Additional context

Somewhat related to #2847

[pwang2]

Is there any follow up on this? As the new year 2023's approaching, we all are thinking about updating our tsconfig.json to be moduleResolution: "NodeNext".

[cjholowatyj]

Any progress on this? TIA

[XavierVilaRubio]

After almost a year and a half this got 0 attention? 🥲
I'm trying to build a project with this tsconfig.json:

{
  "compilerOptions": {
    "esModuleInterop": true,
    "skipLibCheck": true,
    "target": "es2022",
    "allowJs": true,
    "resolveJsonModule": true,
    "moduleDetection": "force",
    "isolatedModules": true,
    "moduleResolution": "NodeNext",
    "module": "NodeNext",
    "outDir": "dist",
    "sourceMap": true,

    "strict": false,
    "jsx": "preserve",

    "lib": ["es2022", "dom", "dom.iterable"],
    "types": ["vite/client"]
  },
  "include": ["./src/**/*"]
}

and I'm getting TS2307: Cannot find module 'primevue/config' or its corresponding type declarations. on build step...

Any idea on how to solve it?