vite icon indicating copy to clipboard operation
vite copied to clipboard

Next generation frontend tooling. It's fast!

Results 600 vite issues
Sort by recently updated
recently updated
newest added

### Description The warning has been outdated since the introduction of `modernTargets`.

### Description fixes #12990 In the following manual tests the `alias` playground is opened in the left terminal, which runs the preview server. In the right terminal, a `SIGTERM` signal...

### Describe the bug I created react project with vite typescript. My problem's is using the library [@undecaf/zbar-wasm](https://github.com/undecaf/zbar-wasm). ### BarcodeScanner.jsx ```javascript import { scanImageData } from "@undecaf/zbar-wasm" const scanBarcode =...

pending triage

### Describe the bug Why does this WARN occur when building a react project with vite? It's very strange (my environment is based on the latest one) ```bash ➜ pnpm...

pending triage

### Description When a `require` is performed the modules resolution currently prioritizes the [`mainFields` option](https://vitejs.dev/config/shared-options.html#resolve-mainfields) over the fact that a `require` has been used, this (especially given the default `mainFields`...

### Describe the bug ``` PS D:\dddd> npm create vite@latest > npx > create-vite √ Project name: ... vite-project √ Select a framework: » React √ Select a variant: »...

bug: upstream

### Description mimic webpack's behavior, providing users with access to default options. [webpack docs](https://webpack.js.org/configuration/resolve/#:~:text=Note%20that%20using%20resolve.extensions%20like%20above%20will%20override%20the%20default%20array%2C%20meaning%20that%20webpack%20will%20no%20longer%20try%20to%20resolve%20modules%20using%20the%20default%20extensions.%20However%20you%20can%20use%20%27...%27%20to%20access%20the%20default%20extensions%3A) [webpack usage](https://github.com/webpack/webpack/blob/2953d23a87d89b3bd07cf73336ee34731196c62e/lib/config/defaults.js#L1458-L1470)

### Describe the bug vite.config.js: ![image](https://github.com/vitejs/vite/assets/71685145/46f183f4-5c82-4927-a1ca-8f84057fc809) entry: ![image](https://github.com/vitejs/vite/assets/71685145/9c93e0de-8b7e-4e57-a6dc-f23dc7e6af8b) output: ![image](https://github.com/vitejs/vite/assets/71685145/d6b33e07-ed64-4b68-a0ef-10f3434fb1e8) I was using single-spa in my project, so I followed the config on the single-spa [docs](https://single-spa.js.org/docs/ecosystem-vite/#configuration). Then, I found that...

pending triage

### Describe the bug Vite does not output html or css when the `@vitejs/plugin-legacy` plugin is used Possibly related to #3279 but that issue was closed ### Reproduction https://stackblitz.com/edit/vite-c4bxea?devtoolsheight=33 Reproducible...

plugin: legacy
p3-minor-bug

## Context Vite currently bundles the config file during development using ESBuild and all the relative imports are marked as "no external" because they are not matched in [this regex](https://github.com/vitejs/vite/blob/6a085d0467ca3b044b4f2108a323af3305a0eae7/packages/vite/src/node/config.ts#L1125),...