svelte-actions VS rfcs

Svelte Actions: A Prototype of Svelte actions for inclusion into official actions in the future.

You might be interested in https://github.com/sw-yx/svelte-actions

There is also an open RFC to add inbuilt actions to Svelte, similar to how Svelte includes inbuilt transitions. As part of that RFC, the community created a POC library with some commonly-used actions such as longpress, clickOutside, and lazyload.

There's an issue open already and a RFC: https://github.com/sveltejs/svelte/issues/6059 https://github.com/sveltejs/rfcs/pull/64

The RFC ticket is here, so if anyone could provide valid use cases, please do it and push hard to make this happen: https://github.com/sveltejs/rfcs/pull/34

In the state Svelte is as of this day, there are a few bumps making it harder to implement versatile sets of UI primitives / atomical components. Namely, some of the ones I've met are: lack of syntax to cleanly forward directives and transitions to a component's template (https://github.com/sveltejs/rfcs/pull/60), lack of default slot assignment (i.e. automatically assigning a child component to a parent's slot without requiring devs to manually specify slot="..."), inconsistent bind:group behavior when used on components with nested inputs or through a store passed with setContext, etc. I don't have as much experience trying to implement such UI library components with other frameworks I've used (Vue, Angular) so I can't really say for sure that these challenges are confined to Svelte.

Good stuff. The conditional wrapper unfortunately doesn't work with directives, but the forward directive RFC would address that.

(Also a con): It's funny to me that a lot of people try to change Svelte to be "light-React" (see the Svelte RFCs). This also tells a lot about React too, it shows what React nails right on the head and what it misses horribly where Svelte got it right.

It's part of this proposal: https://github.com/sveltejs/rfcs/pull/38

Exclusive to elements: Like most Svelte directives (with the exception of on:), this does not work on components. There is an open RFC to allow forwarding directives to components, which would include style directives. However, this RFC has not been accepted at time of writing.

since v3.38.0 https://github.com/sveltejs/rfcs/pull/13 it not yet documented

All of these issues are very valid. For forwarding, I highly suggest you take a look at this RFC I wrote which will make this much https://github.com/sveltejs/rfcs/pull/60