Bjorn Lu

Putting a note that I'll probably come around and rebase this soon. I'm refactoring some resolve stuff, and if all goes well this PR would help remove our reliance on...

Ah my wording in the other PR accidentally closed this. Nonetheless, I'm still working on a fix locally and it'll be quite different from this PR, so there will be...

I think it's a nice to have if it's simple to support, but with the html fallback this makes it a bit complicated. - Should we support reading from both...

We need patak's review to be resolved and tests for this. One way we could make this non-breaking is an experimental option to enable this feature, which could be a...

FWIW I was able to workaround it by implementing [this trick](https://github.com/withastro/astro/blob/8dd43db93f9466b50f8b635c693589c86ef762e3/packages/astro/src/vite-plugin-config-alias/index.ts#L101-L136) on the plugin side. Given most plugins don't need to tap into `createResolver` for CSS etc often, I'm slightly...

Currently Vite automatically preloads dynamic imports by default (`rel="preload"`), which should work better than prefetch in most case. Does this feature currently doesn't work for you? Or if there's a...

`import.meta.hot` intellisense should be set similar to https://vitejs.dev/guide/env-and-mode.html#intellisense-for-typescript. Feel free to update the docs with that info though.

I don't think so. Feel free to take it!

Shouldn't [this](https://vitejs.dev/guide/env-and-mode.html#intellisense-for-typescript) fix the issue? I was suggesting to add a similar info of that to the plugin API docs too.

`vite.config.js.timestamp-1659277944620.mjs` is a file bundled by Vite to read the config file. It happens for TS by default in Vite 3.0.0, and expanded to do so for JS too in...