svelte

Commit Graph

Author	SHA1	Message	Date
Simon H	c603553e89	docs: fix ComponentProps info (#13827 ) * docs: fix ComponentProps info closes #13770 * fix	11 months ago
José Pablo Ramírez Vargas	95980d1f08	feat: Define the MountOptions type (#13674 ) * feat: Define the MountOptions type * Revert "feat: Define the MountOptions type" This reverts commit `bd3596fcba`. * feat: Define the MountOptions type * chore: Add changeset * lint * lint --------- Co-authored-by: Dominic Gannaway <dg@domgan.com>	11 months ago
Simon H	72b066b7fd	feat: allow non-synchronous legacy component instantiation (#12970 ) * feat: allow non-synchronous legacy component instantiation Add a new option to the legacy class component interface so that `flush_sync` can be omitted. Part of https://github.com/sveltejs/kit/issues/12248 * lint --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	1 year ago
Gautier Ben Aïm	f6f0e78cbd	fix: small legibility improvement (#12928 ) * fix: small legibility improvement * Create rich-ladybugs-admire.md * Update rich-ladybugs-admire.md * even better?	1 year ago
Simon H	00e8ebde1d	fix: widen `ComponentProps` constraint to accept more component shapes (#12666 ) language tools has to type its own shape for backwards compatibility, and it currently doesn't include the `$on` and `$set` methods, which means without widening the type as done here you would get a "this shape is not accepted" type error when passing it to `ComponentProps` closes #12627	1 year ago
Simon H	2ea2be3324	docs: explain `runes` compiler option behavior (#12578 ) closes #11523	1 year ago
Rich Harris	72f5539f51	fix: remove runtime validation of components/snippets, rely on types instead (#12507 ) closes #12446	1 year ago
Simon H	919acadc35	fix: bump dts-buddy for better exports type generation (#12262 ) #12202 revealed that TypeScript has a harder time tracing imports when they are indirectly exposed, e.g. `function foo(): void; ... export { foo }` instead of `export function foo(): void;`, which can lead to bugs down the line (such as in that issue). A new `dts-buddy` version fixes this, which in turn fixes #12202 This also adjustes the `Snippet` type and turns it into an interface, which makes for better intellisense: The type will be unpacked in less situations, resulting a more readable and named type.	1 year ago
Tiger Oakes	72fec99b06	feat: improve type arguments for Snippet and $bindable (#12197 ) * Improve type arguments for snippet and bindable * generate:types * tweak * changeset --------- Co-authored-by: Rich Harris <rich.harris@vercel.com> Co-authored-by: Rich Harris <hello@rich-harris.dev>	1 year ago
Naser Aleisa	60d90a9b60	docs: demonstrate how to infer a component's props type (#12038 )	1 year ago
Simon H	8388c4d90e	chore: add `@description` tags (#12063 ) add them so that the TypeScript parser doesn't put the following content under the `@deprecated` tag, which messes with the JSON-type-generation script.	1 year ago
Simon H	9dc2d71a12	fix: relax constraint for ComponentProps (#12026 ) `Component` with any props should be allowed to pass in	1 year ago
Ignatius Bagus	1ecbbc0914	docs: remove `createRoot` references (#12018 ) * docs: remove `createRoot` references * changeset	1 year ago
Dennis Dudek	84ad208f2e	Svelte5 (Types/Doc) import Component as Type (#11992 ) * import Component as Type interfaces can only be used as a Type, that way it should be imported as type * fix import type * regenerate types --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	1 year ago
Simon H	5b0a843b31	fix: relax `Component` type (#11929 ) The current type narrows the binding type to `""` by default, which means "no bindings on this component". While this is the common case, it makes it very cumbersome to use the `Component` type because legacy components are of type `string` and as soon as you have bindings, the type is something like `"foo" \| "bar"` which _also_ is not assignable to `""` which is semantically wrong, because you should be able to assign a component that can have bindings to a type that accepts none. The pragmatic solution is to change the binding type to allow `string`, which means someone theoretically could use bindings with a component that doesn't have bindings: ```svelte <script> let component: Component<{ prop: boolean }> = IAcceptNoBindings; </script> <!-- allowed but should be a type error --> <svelte:component this={component} bind:prop={foo} /> ``` But this is a) rare anyway and b) can be caught at runtime This came up in comments of #11775	1 year ago
Simon H	8c66b64e6b	feat: provide new `Component` type that represents the shape of components (#11775 ) In Svelte 3 and 4, components were classes under the hood, and the base class was `SvelteComponent`. This class was also used in language tools to properly type check the template code. In Svelte 5, components are functions. To give people a way to extend them programmatically, it would be good to expose the actual shape of components. This is why this PR introduces a new `Component` type. For backwards compatibility reasons, we can't just get rid of the old class-based types. We also need to ensure that language tools can work with both the new and old types: There are many libraries out there that provide `d.ts` files with type definitions written using the class types - these should not error. That's why there's an accompagning language tools PR (https://github.com/sveltejs/language-tools/pull/2380) that's doing the heavy lifting: Instead of generating classes, it now generates a constant and an interfaces and uses Typescript's declaration merging feature to provide both so we can declare a component export as being both a class and a function. That ensures that people can still instantiate them with `new` (which they can do if they use the `legacy.componentApi` compiler option), and it also ensure we don't need to adjust any other code generation mechanisms in language tools yet - from a language tools perspective, classes are still the norm. But through exposing the default export as being _also_ callable as a function we can in a future Svelte version, where classes/the Svelte 4 syntax are removed completely, seamlessly switch over to using functions in the code generation, too, and the `d.ts` files generated up until that point will support it because of the dual shape. This way we have both backwards and forwards compatibility.	1 year ago
Simon H	a038d49f78	fix: rework bindable types strategy (#11420 ) Instead of using types that declare whether or not a type is bindable directly as part of the property, we're introducing a new for-types-only field to `SvelteComponent`: `$$bindings`, which is typed as the keys of the properties that are bindable (string by default, i.e. everything's bindable; for backwards compat). language-tools can then produce code that assigns to this property which results in an error we can display if the binding is invalid closes #11356	1 year ago
Simon H	f6dfac985c	feat: `Bindable` types (#11225 ) This is a typings PR and the companion PR to sveltejs/language-tools#2336 It introduces two new types: - Binding: Marks a property as being bound (i.e. you must do bind:x) - Bindable: Marks a property as being able to be bound (i.e. you can do bind:x) Language tools then uses this generate code accordingly which then generates type errors. All the other type gymnastics are there to ensure that you don't interact with these bindable types when using mount or hydrate or ComponentProps<MyComponent>, i.e. these two types should be mostly opaque for day-to-day users. For backwards-compatibility, all properties are automatically wrapped with Bindable, which means existing type definition files will continue to work from a types perspective. Language tools opts into strict bindability by providing its own constructor definition for all generated classes in runes mode which omits the "wrap everything with bindable" behavior.	1 year ago
Simon H	b1a8038f8b	fix: make static `element` property available (#11079 ) for the SvelteComponent type closes #8936	1 year ago
Rich Harris	eaa243d2da	chore: reshuffle some code (#10967 ) * remove superfluous .d.ts file * remove main/main-client.js to index-client.js * move main/main-server.js to index-server.js * move main/public.d.ts to index.d.ts * move ambient.d.ts * fix * fix	1 year ago

20 Commits (c603553e89a3affcb4cea0c4fa4923430aacfad1)