Bjorn Lu

I think we can close this with https://github.com/vitejs/vite/pull/17709 merged

Vite doesn't respect the tsconfig paths today, hence I don't think we should fix the problem this way. Similarly in https://github.com/vitejs/vite/issues/6828 where we had discussed and decided that we don't...

> The issue you mentioned is about resolving tsconfig paths across the entirety of Vite. This isn't trying to do that, or replicate/replace vite-tsconfig-paths or similar plugins. It's specific to...

Related https://github.com/vitejs/vite/issues/16718 Closing this as it's not something we want to support in the config.

I think the `require` here is still valid as it's used within a dependency (axios). Looks like the issue here is that axios specifies a [browser field](https://github.com/axios/axios/blob/62d8eb793eb1cfd925923ff9c5855189ced9bce1/package.json#L98-L101) which Vite respects,...

I've yet to thoroughly review this, but wondering, could this be refactored in `main`? Seems like a nice general refactor otherwise so we keep the environment API changes small. Or...

Seems like a nice addition, but we probably can't add this until the next major since it could collide with other Vite plugins that uses `?buffer` for something else. A...

I'm not sure about your point with `ArrayBuffer` and `SharedArrayBuffer` since we're reading the file as a buffer itself. But I could see the scope grow with needing Int32Array etc...

When I run `npm install`, I get: ```bash bjorn@Bjorns-MacBook-Pro vite-project % npm i npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While...

Ah yeah for the JS template, I get: ```bash npm error Could not resolve dependency: npm error peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8" from...