Albert Marashi

> It's most likely because there isn't a type definition for the custom element and unrelated to this issue. You'll need to enhance the typing https://svelte.dev/docs/typescript#enhancing-built-in-dom-types. You can use the...

@jasonlyu123 yeah with my workaround, sure, but I don't understand why the fallback case shouldn't be `HTMLAttributes` instead of `{ [name: string]: any }` which creates a tonne of `parameter...

@jasonlyu123, why wouldn't SVG Elements have their own key in `SvelteHTMLElements` which would take precedence?

 This is _**extremely**_ annoying and I feel like the correct behavior in this scenario is to default to `HTMLElement` because that's how browsers treat it regardless.  As you...

@dummdidumm does it make sense then to do: ```ts interface SvelteHTMLElements { [name: string]: HTMLAttributes // or [name: string]: HTMLAttributes & { [key: string]: any } } ```

> The more upvotes this gets will equal to the priority!! If it's a big must - I'll try my best to implement it! 125 now.. Any news on progress

I would like to raise a point. Vue code should be universal, and you shouldn't ever need server-side libraries in a vue app, I would consider that an anti-pattern since...

Ok, the docs should at least be fixed in that case since they contradict

Simpler min reproduction ### Describe the bug Cannot perform division by 0 when updating record using `math::mean()` in aggregate view, possibly due to `UPDATE` operation doing a reduction in the...

Also got this issue