History

Simon H 9a99554379 breaking: remove Component type, keep using SvelteComponent instead (#9413 ) I came to the conclusion that when we're making up arbitrary types, we might as well keep the old class. That way: - one less thing to worry about (language tools and other tooling basically can continue to spit out SvelteComponent ) - we can more clearly mark $set , the constructor etc as being deprecated and no longer functioning unless you use that legacy compatibility mode - much more ergonomic to type for the user: - const someInstance: SvelteComponent<..> instead of const someInstance: ReturnType<typeof Component<..>> - If you're using generics, you can do export class MyComponent<T> extends SvelteComponent<{ prop: T }> {} instead of having to type out the whole function in a way that I'm not even sure how to do with generics		1 year ago
..
README.md	…
config.json	…
moody-owls-cry.md	…
pre.json	…
rotten-buckets-develop.md	…
small-papayas-laugh.md	breaking: remove Component type, keep using SvelteComponent instead (#9413 )	1 year ago
tall-shrimps-worry.md	…

README.md

Changesets

Hello and welcome! This folder has been automatically generated by @changesets/cli, a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it in our repository

We have a quick list of common questions to get you started engaging with this project in our documentation