Is your feature request related to a problem? Please describe
In my component's props TS interface, I can use JSDoc comments to set the description, and can even use the @default tag to describe the default value 💯
However, nothing happens when I use the @deprecated tag.

Describe the solution you'd like
Some ideas:

• It would be nice i

I have an podcast with episode uploaded to Mixcloud. I also have my music uploaded to Soundcloud. I'd like to see Mixcloud and Soundcloud added as providers with Vime.js

Also I endorse the feature request for playlist.

I plan to use this with an Svelte app.

IconButton does not 'blur' when it loses focus, retaining it's --background-focused class after the mouse or touch leaves the item.

This file is currently imported in mystyles.scss. It corresponds to a bulma feature.

This is all and well, but long term we want to avoid using bulma, and instead implement the styles within each component. The advantage of that is that we don't have to put unused CSS on page

The various popup shown can be placed outside the viewport, making them hard to view/use.

For example, a tooltip can be partially hidden if the activator is in the right of the screen, or a menu can be longer than the viewport height.

Smelte should probably provides utils to position popup on the viewport.

(by the way, thanks for your work, smelte is great :)

Is your feature request related to a problem? Please describe.
Hello team.
I have a task to deploy a tiny and cute frontend, which will distribute wg configs for users of our organization. I decided to use your package, because it is 100% suitable.
We use dedicated server as a wg endpoint (VyOS cluster on vrrp), so I don't need to create peers from UI. I am populating config.json by ansible

It would be good to have some kind of performance tests to get a better understanding of how well the extension performs, and to keep track of it to not overlook accidental performance decreases when adding new things.

The performance tests as a start could consist of:

• One autocompletion inside script (means svelte2tsx and the TS service are tested)
• One diagnostic run on a file that needs

I use a custom transition when going from/to my intro/outro scene to my live scene, but use the standard fade transition when live to switch between different scenes that have different camera views. I need to be able to select which transition I want to use before executing a scene change. According to the websocket documentation, it should be possible to show the available transitions in the web