Bjorn Lu

> * `.css?raw&url` now returns a URL to raw CSS Is there a reason this is supported? I can't quite think of a case where a user would use this,...

Yeah I think this is a breaking change and we can't bump this until v6. Unless we can still get `ts-node` working partially, but it doesn't seem likely now with...

You can pass a string to `server.open` to point to the network url.

It's in the Vite docs: https://vitejs.dev/config/server-options.html#server-open ```js server: { open: 'http://10.23.44.14:8080/' } ```

I guess thinking about it, you might not want the network url to not be hardcoded. You can try to resolve the `0.0.0.0` in your Vite config, then pass the...

I'll re-open for now if anyone has ideas to supporting this. We usually avoid adding new options unless if there's a large usecase. I'm thinking maybe we can flip this...

`targets` is the legacy target, so I don't think `await detectPolyfills(raw, options.targets, modernPolyfills);` is correct? Maybe we can introduce a new `modernTargets` option. Until there's a way for us to...

@C-Higgins Making `targets` implicitly elevate as modern targets is a bit too automatic, especially that the default targets are set to target older browsers `'last 2 versions and not dead,...

@jgosmann If we introduce a new `modernTargets` option that's a browserlist query, then yes we can use the package to turn that into esbuild syntax. I was referring before that...

Vite currently can't omit the `__vitePreload` because the dependency array can only be retrieved during the `generateBundle` phase (after Rollup has chunked everything). So Vite can only preemptively guess that...