Alec Larson

> This means that SvelteKit's adapters now have to know how to map SvelteKit routes to the routing functionality of each hosting platform. I've talked a bit about Saus recently...

@benmccann Is there actually a need for multiple builds in `vite.config.ts` files, or is support through programmatic API enough? That would avoid the breakage of other tools that load Vite...

I see some people are encountering this with `vite dev`. In that case, you should (1) connect the Chrome inspector to your Vite process and (2) pause the step debugger...

Hi @nichita-pasecinic, please see [this comment](https://github.com/vitejs/vite/issues/2433#issuecomment-1026248109): > would also help to get an actual simple reproduction in a github/stackblitz repo

**Note:** This isn't a React-specific or Vite-specific issue, but a Rollup issue (specifically with their CommonJS plugin). ## The Workaround Example: https://github.com/alloc/vite-react-jsx/commit/2db2870f5ad888ed7d4a57e5ba10a82f8bdf80b2 Instead of importing the CJS package directly, use...

@smajl My goal is to increase my sponsor count. I'm the only React-focused maintainer of Vite, so if any of you use React, please sponsor me, or I can't justify...

Hi @juspky. Another PR has been merged that allows Vite to stop using `@rollup/plugin-commonjs` in production builds (see #8280). You should test Vite's latest alpha version and report back if...

I don't understand why `__reExport` is used (at all) when the target format is ESM?

@fiznool Is that the only documentation? Seems sparse.

I forked this repo and updated it to use [**jasmine-core**](https://www.npmjs.com/package/jasmine-core) instead of embedding Jasmine as part of this package. So you should (in theory) be able to use any version...