Patrick Nelson

Closing this for now since it’s stale (nearly a year old). Can open again if you find something in `svelte-retag` (again, not supporting other libraries or packages modifying the contents...

Tagging for `v2` milestone for now, given it's more likely to be easier to implement once we are already stadardized on the `customElement` syntax.

Added explicit set of desired features in order of priority (must have vs. nice to have) to help explicitly call out desire to perform type coercion (as requested in #26...

Quick note: Clarified that this will be for **supported features only**, i.e. either features that already exist or ones being added specifically in this ticket (e.g. custom attribute names and...

**Note:** This may actually only affect IIFE-based execution which embeds styles in the JS and then tries to attach them to the main document. If compiling using the typical modules,...

Probably related to https://github.com/vitejs/vite/issues/11769. Maybe just specific to compiling to `umd` or `iife` in Vite, causing the styles to be injected on the host page instead of making them available...

Reverting title again, since there are actually multiple use cases for this (i.e. missing styles when using the shadow DOM): 1. **IIFE/UMD:** As noted above, styles are always only ever...

Right now: No, since it's still unstable and actively under development (at time of writing). _However_, we can at least anticipate what's coming up with some of the public API...

p.s. Forgot to mention that as part of my testing in `experimental-svelte-v5` branch, I went ahead and rolled out #27 as a minor/patch fix, which was necessary to address some...

> It can check for internal version and support both v3+v4 and v5. Here is the relevant [file](https://github.com/sveltejs/svelte/blob/a31b2e1b8e6638aa0d652afdd4cc958436dfeacd/packages/svelte/src/version.js#L9) in svelte repository that exposes svelte version. In this case, my key...