Use the SvelteComponent interface for typing components #412
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, component TypeScript definitions in this library mock the internal Svelte component API so that it is readable by the Svelte Language Server. This practice is discouraged because properties like
$$prop_def
and$$slot_def
are intended to be private.Released in version 3.30, Svelte supports components definitions that use the typed SvelteComponent interface. Refer to the accepted RFC for more info.
The new SvelteComponent interface provides a nice API to type props, events, and slots through generic parameters.
Before (discouraged)
After
Breaking Changes
Although there are no API changes, TypeScript users will need Svelte version 3.30 or greater.