quokka
quokka copied to clipboard
wallabyjs
Support for VueJS Single File Components
I currently use WallabyJS. It appears to work with .vue files just fine. Any chance quokka can support .vue files?
Thanks!
Visual Studio Code v1.23.0 OSX 10.13.4
At the moment Quokka doesn't support .vue files, so marking it as a feature request.
@sandro-git that this is the only thing that keeps be away from buying pro license
What would your ideal experience look like if we added support for Vue in Quokka? Is support for single file components only enough to be useful? I assume you would also want HTML elements hoisted into a DOM for your code to run against?
@smcenlly I think for start it would be useful just to work on js side.
Everything else can be added later.
@smcenlly - Does your question mean there could be some vue support soon? If so, what's the target rollout (i.e. when might we see some support)?
I agree with this.
On Thu, 18 Oct 2018 at 04:14, Alan Aasmaa [email protected] wrote:
@smcenlly https://github.com/smcenlly I think for start it would be useful just to work on js side.
Everything else can be added later.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/wallabyjs/quokka/issues/198#issuecomment-430861127, or mute the thread https://github.com/notifications/unsubscribe-auth/Af-f0D6O32ubcTO4Kq8Emwn3o4qQQnXuks5ul_IGgaJpZM4TyOuJ .
@smcenlly - Does your question mean there could be some vue support soon? If so, what's the target rollout (i.e. when might we see some support)?
At this point in time we don't have a date we can share re: target rollout.
We did some preliminary investigation last week hoping that adding support for Vue would be relatively simple. There's a bit of complexity integrating this with Quokka's existing TypeScript and Javascript instrumentation as we need this to work with zero configuration across Vue 2.x vs Vue 3.x and both TypeScript vs. Javascript. At this point in time we don't expect to continue working on this until late December at the earliest.
@smcenlly - I'd be lying if I said I wasn't disappointed with your answer. Regardless, I really appreciate your response! Knowing when to expect, or not expect, something is still super useful information. Of course, I'll be happier when vue is supported. 😉
I understand the complexity of full integration with vue versions and whatnot. Perhaps enabling code between <script> tags wouldn't be too much to engage. We can always expand coverage into the html expressions and bindings later. This alone would be a huge boost to vue productivity obvz. ty for the tools!
