Setting initial route fails when routes have dynamic import

Describe the bug There is a test which shows that initialising a router can be done by pushing a path. We use dynamic imports to lazy load our routes. In combination, this results that the initial route is not set at all. https://github.com/testing-library/vue-testing-library/blob/d628f36b6122e629553d388a9c4953fc5cb2e1ab/src/__tests__/vue-router.js#L29-L31

To Reproduce Change the following line to

{path: '/about', component: () => import('./components/Router/About.vue')},

and run the tests. https://github.com/testing-library/vue-testing-library/blob/d628f36b6122e629553d388a9c4953fc5cb2e1ab/src/__tests__/vue-router.js#L10

Expected behavior I expected that to work right out of the box or with help of waitFor or something… But I did not manage to get it working.

[afontcu]

Hi! Thanks for the extensive reporting and for working on this 🤗

I feel too that changing the public render interface to a Promise is a big deal. It would solve, however, several issues I encountered regarding the first “tick”, where stuff in mounted() or created() is not executed until we await one clock tick.

It is a big deal, but I wonder if there’s any workaround on this. I’ll give a look soon and see what I can come up with!

Have a nice day 😄

[afontcu]

I feel the suggestion above is valid enough so that we don’t need to overcomplicate router setup. As mentioned, VTL provides a comfortable way to set up the store and router, but you can always get the Vue instance and use it in your favor.

Thanks for posting this, though! 👍 It’ll be really helpful for anyone else running into issues with dynamic imports.

Closing it up!