7nik
7nik
For now, it will be too confusing with legacy/svelte4 prop declaration. Exporting function is allowed because its semantics didn't change, but for exported variables it would mean that it defines...
Please, add a test that fails without this fix. Propably it should go to the `hydration` folder, you can at the `input-value-changed` test as example of what you need.
These directives add `class`/`style` attribute to the element, so the attribute selectors can match them but, before this fix, could fail in some cases. If there is a real bug...
@mattpilott I don't really get what gets broken in your example. Can you test on #16204?
That PR fixes this repro.
From [WHATWG specs](https://html.spec.whatwg.org/multipage/custom-elements.html#valid-custom-element-name) * name must match the `PotentialCustomElementName` production: * `PotentialCustomElementName` ::= `[a-z] (PCENChar)* '-' (PCENChar)*` * `PCENChar` ::= `"-" | "." | [0-9] | "_" | [a-z] |...
> the user has not formally entered text If you imply that the semi-composed text is meaningless, then the same can be said about the unfinished word or sentence/query. A...
Svelte doesn't have modifiers. The simplest way is ```svelte composing = true} on:compositionend={() => composing = false} /> ``` and do nothing when `composing` is `true`.
See https://github.com/vitejs/vite/issues/15890 for the info. Maybe the svelte compiler should drop unused imports but not imports itself.
Maybe `build_expression` should apply to `@render`'s arguments as well. And changes to the each-index-non-null test now can be reverted.