You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started receiving this error upon using ValidationMessage
Argument of type 'typeof ValidationMessage' is not assignable to parameter of type 'ConstructorOfATypedSvelteComponent'.
Type 'typeof ValidationMessage' provides no match for the signature 'new (args: { target: any; props?: any; }): ATypedSvelteComponent'.
Possible causes:
- You use the instance type of a component where you should use the constructor type
- Type definitions are missing for this Svelte Component. If you are using Svelte 3.31+, use SvelteComponentTyped to add a definition:
import type { SvelteComponentTyped } from "svelte";
class ComponentName extends SvelteComponentTyped<{propertyName: string;}> {}ts(2345)
Apologies for the delay! Is this still happening to you? If I remember correctly, newer versions of Svelte use SvelteComponent instead of SvelteComponentTyped. Does it still happen with more recent versions of Svelte?
Yes, we patched it with a custom type. But on that note, if you upgrade to svelte 5...
**
* This was the base class for Svelte components in Svelte 4. Svelte 5+ components
* are completely different under the hood. For typing, use `Component` instead.
* To instantiate components, use `mount` instead`.
* See [migration guide](https://svelte.dev/docs/svelte/v5-migration-guide#Components-are-no-longer-classes) for more info.
*/
export class SvelteComponent<
Props extends Record<string, any> = Record<string, any>,
Events extends Record<string, any> = any,
Slots extends Record<string, any> = any
>
Describe the bug
I started receiving this error upon using
ValidationMessage
I think it can be fixed by changing this
to this
Which package/s are you using?
@felte/reporter-svelte
Environment
To reproduce
No response
Small reproduction example
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: