Franco Lucchini

This bug is very annoying but there's a workaround: ```ts if (import.meta.env.PROD) { var modelValue = toRef(props, 'modelValue') } ``` it's a ugly but it works, the only thing you...

In my opinion user should be free to use any css preprocessor out there, for example I'm using [rollup-plugins-styles](https://github.com/Anidetrix/rollup-plugin-styles) that's a very good plugin. [Here](https://github.com/franklx/rollup-plugin-vue/commit/58d3e6b1e960b491533bc7d9edf932556ecc56fc) I added a `processStyleTags` to...

I can confirm too: problem persists even with a simple `vue-tsc --noEmit` invocation

Sure, i put up a [test repo](https://github.com/franklx/tmp-test-esbuild) . It contains 2 commits: the working version with 0.14.3 and the non-working version with latest esbuild. You should simply run "node build.mjs"...

My understanding of the (messy) import/export mechanism is poor but I made it work by *explicitly* exporting render and setup functions: ```ts const setup = script.setup; export { script as...

Solution is actually very simple: generated script must use cjs export mechanism: ```diff - code += "export default script;"; + code += "module.exports = script"; ``` My fork includes this...

Now I'm using node v16 but maybe in January I was using v14 (or even v12). I'm still using my fork: I'll try using yours and let you know.