Fixes #79

Wrapping an async component factory leads to classes on the component
instance not being rendere...

Manually Resolving the async factory component is not necessary.

Fixes #75

Fixes #74

Using `apply()` to bind the event listener, leads to the listener
listening on all (?) elements.

Import wrappers and the LazyHydrate component now both use (almost)
exactly the same hydration b...

This change prevents all instances of a component imported via a wrapper
from being hydrated as ...

They now always return the same component instead of a loading component
while waiting for hydra...

Was a copy & paste error.

It never did work as expected and could lead to layout shifts.

`ssr-only` was misleading because there is no hydration on the server.

Update dependencies

Fix the scrolling passive on interactions

This is a fix for lighthouse complaint.

Bumps [acorn](https://github.com/acornjs/acorn) from 5.7.3 to 5.7.4.
- [Release notes](https://g...

Fixes #19

Fixes #31

Fix security issues with dependencies

Benchmark CLI tooling

Vue.js checks if `vnode` is an `asyncFactory` and a comment to skip
further hydration check logic.

Polyfilling async / await is not so easy to do so before this package
did only work if the async...

See https://github.com/maoberlehner/vue-lazy-hydration/issues/19

https://github.com/vuejs/vue/issues/9847
https://github.com/maoberlehner/vue-lazy-hydration/issu...

The wrong element was observed which lead to components not being
hydrated when the became visible.