I know buble produces faster code, and I imagine that is why you use it. I've found two issues:
the rest operator does not work inside of vue components only - it works just fine in, for example, a router.js file. The work-around you applied to get it working in places like that apparently does not apply to the vue component itself, and instead you have to rewrite it to object-assign style.
buble does not, and has never supported async/await. there was 8 months ago, a discussion thread about implementing it in buble, but it was described as contrary to the typical style of buble, and it never was added. I've talked with John Leider about this. I'm just voicing my opinion here for anyone working on the project.
Right now you have to manually convert your async/await functions to promise chains, (or, for example , manually run babel on your source file, copy the changed async/await function, and replace your code with that).
For these reasons, especially the second, which requires some more serious rewriting ont he part of developers in order to work with buble, I feel going back to babel is worth the performance hit.
We talked about this in gitter. Your suggestion was in reference to the webpack template, which can be changed to babel, vuetify isn't reliant upon buble.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord
I know buble produces faster code, and I imagine that is why you use it. I've found two issues:
the rest operator does not work inside of vue components only - it works just fine in, for example, a router.js file. The work-around you applied to get it working in places like that apparently does not apply to the vue component itself, and instead you have to rewrite it to object-assign style.
buble does not, and has never supported async/await. there was 8 months ago, a discussion thread about implementing it in buble, but it was described as contrary to the typical style of buble, and it never was added. I've talked with John Leider about this. I'm just voicing my opinion here for anyone working on the project.
Right now you have to manually convert your async/await functions to promise chains, (or, for example , manually run babel on your source file, copy the changed async/await function, and replace your code with that).
For these reasons, especially the second, which requires some more serious rewriting ont he part of developers in order to work with buble, I feel going back to babel is worth the performance hit.