Bjorn Lu

This sounds similar to https://github.com/vitejs/vite/issues/5966 which is requesting for a more lenient HTML parser. Currently we're using Vue's parser for HTML but we may have to explore other parsers to...

I tested the repro with Vite 2.9.13 and plugin-react 1.3.2, and it seems to work fine. [Stackblitz](https://stackblitz.com/edit/github-wcgjsd?file=src%2FApp.jsx). So this might be a regression in Vite 3.

At https://github.com/sveltejs/kit/issues/4795, @Axeldeblen provided a repro (https://github.com/Axeldeblen/realworld-big-build) with sveltekit which is failing on the vite ssr build phase. It should be relevant here too as sveltekit doesn't do a lot...

This feels like a very niche usecase which many plugins won't support, so it's not only a problem with plugin-vue. What is your usecase needing to accessing Vue components from...

You shouldn't be using `process.env.NODE_ENV` in your source code. There's `import.meta.env.DEV` and `import.meta.env.PROD` for those, so I don't think Vite should be adding the types for it, even though it...

`process.env.NODE_ENV` is a standard in nodejs only. There's no `process` in the browser, hence Vite introduce `import.meta.env` for it. It's common for libraries to use them, even if they are...

This seems to be a bug where SSR is trying to load `dom-to-svg` as `/node_modules/.vite/deps/dom-to-svg.js` which is only used for client code. It should be externalized instead, but I'm not...

Looks there are failing tests before it can be reviewed.

This would also help with [environment-specific imports](https://github.com/vitejs/vite/discussions/4172), since the `?client` and `?server` suffixes cause a lot of issues with intellisense. Import assertions would help alleviate this (and maybe other Vite...

Is there anything specific Vite has to cover for import assertions? We've updated our dependencies (esbuild, es-module-lexer, etc) to already support import assertions. So right now they should be left...