5 Commits (3df9d8466f712be14c99542f6a696f96db087b4d)

Author	SHA1	Message	Date
S. Elliott Johnson	fd9d61a7b7	chore: TS to JSDoc Conversion (#8569) ... --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	2 years ago
Simon H	d083f8a3f2	feat: custom elements rework (#8457) ... This is an overhaul of custom elements in Svelte. Instead of compiling to a custom element class, the Svelte component class is mostly preserved as-is. Instead a wrapper is introduced which wraps a Svelte component constructor and returns a HTML element constructor. This has a couple of advantages: - component can be used both as a custom element as well as a regular component. This allows creating one wrapper custom element and using regular Svelte components inside. Fixes #3594, fixes #3128, fixes #4274, fixes #5486, fixes #3422, fixes #2969, helps with https://github.com/sveltejs/kit/issues/4502 - all components are compiled with injected styles (inlined through Javascript), fixes #4274 - the wrapper instantiates the component in `connectedCallback` and disconnects it in `disconnectedCallback` (but only after one tick, because this could be a element move). Mount/destroy works as expected inside, fixes #5989, fixes #8191 - the wrapper forwards `addEventListener` calls to `component.$on`, which allows to listen to custom events, fixes #3119, closes #4142 - some things are hard to auto-configure, like attribute hyphen preferences or whether or not setting a property should reflect back to the attribute. This is why `<svelte:options customElement={..}>` can also take an object to modify such aspects. This option allows to specify whether setting a prop should be reflected back to the attribute (default `false`), what to use when converting the property to the attribute value and vice versa (through `type`, default `String`, or when `export let prop = false` then `Boolean`), and what the corresponding attribute for the property is (`attribute`, default lowercased prop name). These options are heavily inspired by lit: https://lit.dev/docs/components/properties. Closes #7638, fixes #5705 - adds a `shadowdom` option to control whether or not encapsulate the custom element. Closes #4330, closes #1748 Breaking changes: - Wrapped Svelte component now stays as a regular Svelte component (invokeing it like before with `new Component({ target: ..})` won't create a custom element). Its custom element constructor is now a static property named `element` on the class (`Component.element`) and should be regularly invoked through setting it in the html. - The timing of mount/destroy/update is different. Mount/destroy/updating a prop all happen after a tick, so `shadowRoot.innerHTML` won't immediately reflect the change (Lit does this too). If you rely on it, you need to await a promise	2 years ago
Ben McCann	be645202d6	breaking: remove legacy package.json files (#8515)	2 years ago
gtmnayan	2f423475f7	chore: produce single bundle for runtime with multiple entrypoints (#8504) ... * single runtime bundle * formatting * dedupe output options * fix tests apparently * skip writeBundle for cjs build * revert quotes * remove manualChunks * some node16 module resolution compliance * disable minifyInternalExports (doesn't really make sense for a library since users' build step will do it again anyway)	2 years ago
Ben McCann	2813814396	chore: upgrade rollup (#8491) ... bump to rollup 3. Includes reworking the "treat those imports as external" a bit so that Rollup builds correctly but doesn't bundle some of the (now relative) imports --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	2 years ago