Argument of type 'typeof Popup__SvelteComponent_' is not assignable to parameter of type 'typeof SvelteComponent'.

[KoljaL]

Fist: It works and it works great :-)

But i get an type-error on Popupin the last line:

import { writable } from 'svelte/store';
import Modal, { bind } from 'svelte-simple-modal';
import Popup from '$lib/components/Popup.svelte';
const modal: any = writable(false);
const showSources = (): void => modal.set(bind(Popup, {}));

This is the full error message from VSCode:

Argument of type 'typeof Popup__SvelteComponent_' is not assignable to parameter of type 'typeof SvelteComponent'.
  Types of construct signatures are incompatible.
    Type 'new (options: ComponentConstructorOptions<{ message?: string | undefined; }>) => Popup__SvelteComponent_' is not assignable to type 'new <Props extends Record<string, any> = any, Events extends Record<string, any> = any, Slots extends Record<string, any> = any>(options: ComponentConstructorOptions<Props>) => SvelteComponent<...>'.
      Construct signature return types 'Popup__SvelteComponent_' and 'SvelteComponent<Props, Events, Slots>' are incompatible.
        The types of '$$prop_def' are incompatible between these types.
          Type '{ message?: string | undefined; }' is not assignable to type 'Props'.
            '{ message?: string | undefined; }' is assignable to the constraint of type 'Props', but 'Props' could be instantiated with a different subtype of constraint 'Record<string, any>'.

How do I set the correct Types?

[flekschas]

Sorry about that! Not sure what's going on. I haven't seen that error before. Which version of svelte-simple-modal and svelte have you installed?

[alankrantas]

This happened to me too when I tried to upgrade my Svelte 3 site to Svelte 4. The component type is changed hence the error. https://svelte.dev/docs/v4-migration-guide#sveltecomponenttyped-is-deprecated

Not a bug for Svelte 3 though.

[KoljaL]

Yes, I use #4 too.

[flekschas]

FYI, I have a PR #101 for adding support for Svelte v4. I just need to figure out another type issue that seems to be new since v4