patak

I would prefer to directly wait for Vite 4 and fix this instead of adding the temporal `!browser` option, but if @sheremet-va @antfu thinks fixing this is important enough for...

Thanks for the feedback. @sapphi-red what do you think about renaming to `resolve.browserField` and release it in 3.2?

/ecosystem-ci run

Amazing work @sapphi-red! I think to play safe it is better to merge this one on the 3.2 beta, and we could delete the facade in v4.

I think there is a bug in plugin-react-refresh, but we can not reload on error. Check out the warning message "This could be due to syntax errors or importing non-existent...

We had a related PR to change the order of PostCSS plugins, and have the user ones before the internal ones: - https://github.com/vitejs/vite/pull/7186 In that case, it was closed because...

Another point in favor of waiting here is that there is a chance we end up [replacing PostCSS with LigthingCSS in the future](https://twitter.com/devongovett/status/1569163638015143938?s=20&t=zDT6KuPhdXmREAzeuhmMSg)

> Pushing a WIP, so we can discuss the API, @danielroe @antfu maybe there is a chance to include this in 3.1 (or we can later add it to a...

After [9f1eaa5 (#9938)](https://github.com/vitejs/vite/pull/9938/commits/9f1eaa5f7539eb7588506419465aa8c7251b2efd), `build.modulePreload.resolveDependencies` will be called both for JS dynamic imports preload lists and also for HTML preload lists for chunks imported from entry HTML files. And `experimental.renderBuiltUrl` will...

Thanks for the review @sapphi-red. I would prefer to avoid the name advanced here, and in any case add an Advanced level in docs. This API in particular isn't as...