[bug] private ComponentType interface breaks type declarations

[Theo-Steiner]

Describe the bug

When using tsc to emit types for a svelte 5 project with "declarations": true set in the tsconfig.json, the compilation fails with an error: error TS4082: Default export of the module has or is using private name 'ComponentType'.

(Interestingly, the problem only seems to occur, when a component is passed "through" a generic function, in case of the reproduction: doSth)

Reproduction

https://stackblitz.com/edit/vitejs-vite-fgmgkx?file=src%2Findex.ts

run npx tsc to see how the compilation fails.

Potential fix:
if we go to node_modules/svelte/types/index.d.ts line 2315 however, and modify it to export the interface, the compilation finishes without error.

Logs

No response

System Info

System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Pro
    Memory: 88.94 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.12.0 - ~/Library/Caches/fnm_multishells/75820_1731292463955/bin/node
    Yarn: 1.22.21 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/Library/Caches/fnm_multishells/75820_1731292463955/bin/npm
  Browsers:
    Chrome: 106.0.5249.91
    Safari: 17.5
  npmPackages:
    svelte: ^5.1.9 => 5.1.12

Severity

blocking an upgrade

[dummdidumm]

What is the reason for using tsc to emit types, instead of svelte-package?

[Theo-Steiner]

What is the reason for using tsc to emit types, instead of svelte-package?

This is for a library of web components, so svelte has to be compiled to JavaScript in the build step.
This was (is) not trivial to build with svelte-package.
For this reason we use a custom pipeline when building, that includes emitting types via tsc

[dummdidumm]

I'm wondering if that is of much use, since TS doesn't know anything about the shape of the components - is that a non-problem in your case?

[Theo-Steiner]

Yeah, that's a non-problem in our case.
The user will just register a custom element via a side effect from importing the entrypoint (that's what doSth from the reproduction does in our case).
But internally we make use of the component type returned from doSth to type the props of a custom render function used for testing.
I realize this is not a common use case, but I still don't think returning a generic component type should break typescript