Add support for async components

[eddyerburgh]

We need to add support for async components

[wtho]

Edit: Ok I see it is not related to Webpack, got confused by the docs.

---

How could async components be integrated in the current test setup of this repository? Should webpack provide the possibility to split? Or should we mock statically whatever splitted bundle webpack would serve? Can we test this without extending and rewriting the setup?

Any ideas on this?

I guess this issue also includes advanced async components?

[wtho]

Looking at what the Vue vdom does, my suggestion would be to return a new AsyncWrapper, that first contains a placeholder or nothing, and when the promise resolves or the function calls back, it becomes a normal wrapper.

The tester would then have the need of flushing promises to continue the tests. If flushing promises is not an option, we could expose a loading promise or callback from the AsyncWrapper.

If we do not directly return a wrapper from mount/shallow, we would change the whole library interface.

Does the current setup work, if the child components are async? They should be instantiated by Vue, if I am not wrong?

Any other thoughts so far?

[eddyerburgh]

I haven't investigated into this yet.

You're right, I don't think we should change the behavior of mount and shallow to not return a wrapper. I'll add some more comments when I've had a look into it.

[McSneaky]

Any updates?

[eddyerburgh]

Closing in favor of #61