Are there any benefits for library authors to switch from Actions to Attachments?

[lts20050703]

I am using svelte-dnd-action, and recently I asked the author if there's any plans to switch from Actions to Attachments. The author commented as titled, as well as pointing out that Svelte already provides fromAction for people who need it, though they aren't sure why would anyone need to do so in the first place.

So if a library exist before Attachments and works fine using the Actions system, are there any benefits for library authors to switch from Actions to Attachments?

isaacHagoel/svelte-dnd-action#655

[Ocean-OS]

Actions were developed in Svelte 1.58.2 (#1247) and haven't really evolved since.
Svelte 5's changes didn't really fit with actions, either; the most you could change was tack on an $effect instead of returning update and destroy callbacks. On the other hand, attachments were built using the years of experience with actions— they kept the good parts in mind and improved (or solved!) the bad parts. Attachments have specifically been built for runes and the future. They are composable, providing a simpler, more functional approach to reactively working with the DOM. For (a lot) more information, see the PR for attachments (#15000).

[lts20050703]

I'm sorry, I get what you're saying, but I'm asking that for library authors of a library that was written with Actions and already works fine with the Actions system, are there any benefits for them (or for the library) to rewrite and switch to Attachments?

[brunnerh]

If the actions are exposed to the users of the library, I would recommend switching to attachments.

There is a distinct advantage in that attachments can be passed through components which is not possible with actions.

[lts20050703]

I get what you're saying, but

• That's the benefit to the library users. What about existing actions library authors (as in, is there any QOL for them in writing the code that convince them to spend time migrate from a perfectly fine and functioning use: actions approach)

• Svelte itself already provides fromAction for people who need it (although I am not sure when or why they would). (svelte-dnd-action author)

[brunnerh]

The author side is not that much different but a little bit cleaner. You don't have to deal with update and destroy anymore. This is not a selling point and also should not need to be.

The utility for the user of the library should be the important thing. It is very helpful when using component libraries and you use more components than plain elements.