import of RootContext with redefinition

[dirk-bester]

Current Behavior

node_modules.pnpm@skeletonlabs+skeleton-svelte@4.8.0_svelte@5.46.0\node_modules@skeletonlabs\skeleton-svelte\dist\components\avatar\anatomy\root-context.svelte.d.ts

...
import { RootContext } from '../modules/root-context.js';
declare const RootContext: import("svelte").Component<AvatarRootContextProps, {}, "">;
type RootContext = ReturnType<typeof RootContext>;
export default RootContext;

This yields on pnpm run check:
Error: Import declaration conflicts with local declaration of 'RootContext'.
}
import { RootContext } from '../modules/root-context.js';
declare const RootContext: import("svelte").Component<AccordionRootContextProps, {}, "">;

... \node_modules.pnpm@skeletonlabs+skeleton-svelte@4.8.0_svelte@5.46.0\node_modules@skeletonlabs\skeleton-svelte\dist\components\avatar\anatomy\root-co

In total I am experiencing 27 of them from skeletonui which makes it hard to see anything else. 9/10 AIs agree it is too much error to get inferencing done.

Expected Behavior

maybe do
import { RootContext as <renamed>}
That way the name conflict is avoided.

Steps To Reproduce

svelte 5 project
package.json script:
"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json
run the check, see the errors.

Stackblitz or Reproduction URL

No response

Environment Information

No response

More Information

No response

[Hugos68]

@dirk-bester This actually looks to be a bug with svelte-package, we use svelte-package to package up our svelte components and the output of that should not generate duplicate identifiers, we could indeed rename our imports, but our imports don't conflict in the source code, only in the output. I would suggest opening this exact issue in the Kit repository, let me know if you will or won't do that, otherwise I likely will open up the issue there.

[dirk-bester]

@Hugos68 Let's have you open it please. You can give them better insight into the skeleton side and create tests for it if any.

For completeness, I also see a couple of these:

c:\Users\dirkb\dev\gh\xgrams\node_modules\.pnpm\@zag-js+toast@1.31.0\node_modules\@zag-js\toast\dist\index.d.mts:95:38
Error: Type 'ToastPropsWithDefault' does not satisfy the constraint 'keyof ToastProps<O>'.
  Type '"parent"' is not assignable to type 'keyof ToastProps<O>'.
type ToastSchema<O = any> = {
    props: RequiredBy<ToastProps<O>, ToastPropsWithDefault>;
    context: {

Presumably similar issues via your finite state machine stuff. I did not look into those at all. Maybe just a ts error but without code consequence?

I also do not know if this is a complete iteration of all issues since I don't use all of your components.