mgdodge

Yes, non-minified code would be nice to have, even if it's optional. I was curious to see if the vite library output still suffered from [this treeshaking bug](https://github.com/vuejs/vue-next/issues/2860) (it does),...

I too am using Windows Terminal and WSL2. I am using [`@changesets/cli`](https://www.npmjs.com/package/@changesets/cli) which is based on `enquirer` as my test bed. I have tried the following: - Running XFCE (via...

Any chance of this getting a response?

I agree that the README is confusing - not everyone uses React or tsx, so the examples are not clear. Here is what I pieced together for a clearer example:...

Might give it a try...but the repo I posted is pretty vanilla usage. I would assume that something that "just works" with Vue 2 should be able to upgrade to...

@shubhadip I took a look at the code in that sample repo. I personally couldn't get it to build, but that is beside the point I wish to make -...

Updated to latest 6.0.0 release, and still not fixed. I tinkered with the output a little, and by manually adding the `/*#__PURE__*/` to each call of `styleInject`, `pushScopeId`, and `popScopeId`,...

Will need to reexamine once https://github.com/vuejs/vue-next/issues/2860 lands

Looked at vuejs/vue-next#2860 and things still look broken - see [this comment](https://github.com/vuejs/vue-next/issues/2860#issuecomment-926882793) and the new sample repo mentioned there for details.

The output produced by vite + @vitejs/plugin-vue is really close to perfect, but still has one bug in it. The output from rollup-plugin-vue is a bit further off, but not...