**What's the problem this PR addresses?**
A decent amount of the examples don't have a `name` field in `package.json` that matches their folder name, meaning they either lack a name or the names are duplicated.
I was testing Yarn 2 workspaces using the entire examples directory and needed to get rid of the duplicates.
**How did you fix it?**
Updated the names to match the names of their folders
* Remove outdated examples
* Remove outdated example
* Remove outdated example that doesn't show best practices
* Remove outdated example
* Remove outdated example
* Remove outdated example
* Update preact example
* Update using-router to use useRouter
* Remove outdated example
* Remove outdated example
* Remove outdated example
* Remove outdated example
* Remove outdated example
* Remove outdated example
* Combine examples
* Simplify offered examples
* Remove outdated example
* Add link to new example
* Removed outdated example
* Markdown example has been improved
* Remove example that showed bad practices
* Remove outdated example
* Update polyfills example
* Remove outdated example
* Remove outdated example
* Remove outdated example
* Removed outdated example
* Remove outdated example
* Remove outdated example
* Remove outdated example
* Remove outdated example
* Update webassembly example
* Move example
I wrote a [script](https://github.com/j0lv3r4/dependency-version-updater) to update dependencies recursively in `package.json` files, e.g.:
```
$ node index.js --path="./examples" --dependencies="react=^16.7.0,react-dom=^16.7.0"
```
This PR contains the result against the examples folder.
* emotion v8 + adjustments for breaking changes
* Corrected versioning
* Take hydrate from 'react-emotion'
I was actually wondering that, but haven't seen hydrate in the medium post (even though you pointed out that react-emotion exports all of emotion and I've seen it in source) and didn't want to risk it for the off chance that it *should* be imported directly from emotion for some reason :D