Ricardo Nolde

Hi @uifox Well, that's interesting. I am pretty sure the promise never got resolved, and with such a small polling window (250 ms), it should have been triggered. I will...

Looks like Vue itself already supports multiple roots in functional components. https://github.com/vuejs/vue/issues/7088#issuecomment-345855657

@LinusBorg , my point was about @stalniy mentioning that this issue should be fixed in vue-template-compiler instead of vue-loader. If vue already supports that in functional components, it probably supports...

Tip for people having this issue: use JSX. The JSX loaders for vue support multiple roots by returning an array of components/elements, and it also works around the issue of...

What about using [`vue-demi`](https://github.com/vueuse/vue-demi) to avoid the 1.1.x vs 1.2.x version issues?

`vue-demi` also has no dependencies, it just allows your package to be agnostic without implementing it yourself and, theoretically, it would not affect users of your package (it would not...

Would be nice to have "in-place" namespaces, similar to what happens with `vuex` mappers. ```javascript import { useGetters } from 'vuex-composition-helpers' export default { setup() { const { one, two...

This library is basically dead. I have created [`lambdogels`](https://www.npmjs.com/package/@digitalmaas/lambdogels) to basically upgrade dependencies as temporary support, but I am slowly moving away from vogels/dynogels/lambdogels completely. There are better libraries, such...

I've just deployed a new version. Hopefully it is solved.

Yeah, your method works, but would force to do the resolution of all table names, for all models, at once. My goal would be something like what you mention in...