翠

> By the same token, if the overhead associated with generating an actual SourceMap is not welcome in dev mode (understandable), maybe `importAnalysisPlugin` should use just a regular string instead...

|import|v2 (dev)|v2 (build)|v3 (dev)|v3 (build)| |------|--------|----------|--------|----------| |``import(`./${name}.vue`)``|warning (cannot be analyzed by vite)|warning (Variable imports cannot import their own directory) + error (failed to fetch)|warning (Variable imports cannot import their own...

The error comes from esbuild and it was reproducible only with esbuild. Closing as it is not a bug in Vite. You could create an issue at esbuild repository but...

I suppose `esbuild-plugin-pnp` conflicts with Vite's internal esbuild plugin.

Would you explain why this was happening only when `NODE_ENV=development`? Also IMO we should remove `__source` and `__self` after transformed to JSX instead of avoiding the transform.

> Because the `__self` and `__source` props are automatically added only when `NODE_ENV=development`. > I did some research, I think the root of the problem is `sentry`, which is probably...

About the runtime perf, I'm not sure how much it affects. https://github.com/alloc/vite-react-jsx#faq

> the question is whether this behavior of Vite is intended or not. This is intended. When `lang` or `src` attribute is not defined on ``, it is inlined in...

@stillgbx FYI Your issue is same with #7015. There is the following circular dependency which includes a worker. 1. workers/worker.js 1. services/service.js 1. helpers/helper.js 1. store/store.js 1. components/comp-1/store/store.js 1. components/comp-1/store/actions.js...

~~Instead of this, maybe we should inject a different value for `import.meta.url` depending on output format.~~ done