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

It's important, I think, if the goal is to communicate that this can replace React in more ways than function.

The semantic dom diff plugin uses some global variables like __mocha_context__ and __snapshot__ which are only available in a karma mocha context. When it's user in other test runners, or karma without mocha, it crashes with an unhelpful message.

We should check for these variables, and throw a helpful error to the user that explains this plugin can only be used in Karma.

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.

I'm submitting a ...
[ ] bug report
[ X] feature request
[ ] support request

Current behavior:
Splash screen not showing on iOS

Expected behavior:
Splash screen is showing on iOS, and can be generated through ionic resources

Steps to reproduce:
Launch the application on an iPhone and expect to see a splash screen

Related code:

According to [this article]

Currently the module field on package.json points to src/simpla.js but really it should point to a separate build, that's been transpiled, but not bundled. This means that whatever module bundling system consumers are using will still be used, but it won't need to be transpiled. As it currently stands, users can come up against [this bug](https://github.com/facebookincubator/create-react-app