-import '@babel/runtime/helpers/esm/slicedToArray'+import '@babel/runtime/helpers/esm/slicedToArray'

 function isRefIdentifier(id: Identifier, parent: _Node, parentStack: _Node[]) { const isStaticProperty = (node: _Node): node is Property =>   node && node.type === 'Property' && !node.computed -const isStaticPropertyKey = (node: _Node, parent: _Node) =>-  isStaticProperty(parent) && parent.key === node+const isStaticPropertyKey = (node: _Node, parent: _Node, prop: string) =>+  isStaticProperty(parent) && prop === 'key' && parent.key === node

 export default defineConfig({     port,     strictPort: true,   },-  testConfig: {-    baseRoute: '/url-base/',-  },

-# Migration from v3+# Migration from v4 -## Rollup 3+## Node.js Support -Vite is now using [Rollup 3](https://github.com/vitejs/vite/issues/9870), which allowed us to simplify Vite's internal asset handling and has many improvements. See the [Rollup 3 release notes here](https://github.com/rollup/rollup/releases/tag/v3.0.0).+Vite no longer supports Node.js 14 / 16 / 17 / 19, which reached its EOL. Node.js 18 / 20+ is now required. -Rollup 3 is mostly compatible with Rollup 2. If you are using custom [`rollupOptions`](../config/build-options.md#rollup-options) in your project and encounter issues, refer to the [Rollup migration guide](https://rollupjs.org/migration/) to upgrade your config.+## Deprecate CJS Node API -## Modern Browser Baseline change+The CJS Node API of Vite is deprecated. When calling `require('vite')`, a deprecation warning is now logged. You should update your files or frameworks to import the ESM build of Vite instead. -The modern browser build now targets `safari14` by default for wider ES2020 compatibility (bumped from `safari13`). This means that modern builds can now use [`BigInt`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt) and that the [nullish coalescing operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing) isn't transpiled anymore. If you need to support older browsers, you can add [`@vitejs/plugin-legacy`](https://github.com/vitejs/vite/tree/main/packages/plugin-legacy) as usual.+In a basic Vite project, make sure: -## General Changes--### Encoding+1. The `vite.config.js` file content is using the ESM syntax.+2. The closest `package.json` file has `"type": "module"`, or use the `.mjs` extension, e.g. `vite.config.mjs`. -The build default charset is now utf8 (see [#10753](https://github.com/vitejs/vite/issues/10753) for details).+For other projects, there are a few general approaches: -### Importing CSS as a String+- **Configure ESM as default, opt-in to CJS if needed:** Add `"type": "module"` in the project `package.json`. All `*.js` files are now interpreted as ESM and needs to use the ESM syntax. You can rename a file with the `.cjs` extension to keep using CJS instead.+- **Keep CJS as default, opt-in to ESM if needed:** If the project `package.json` does not have `"type": "module"`, all `*.js` files are interpreted as CJS. You can rename a file with the `.mjs` extension to use ESM instead.+- **Dynamically import Vite:** If you need to keep using CJS, you can dynamically import Vite using `import('vite')` instead. This requires your code to be written in an `async` context, but should still be manageable as Vite's API is mostly asynchronous. -In Vite 3, importing the default export of a `.css` file could introduce a double loading of CSS.+See the [troubleshooting guide](https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated) for more information. -```ts-import cssString from './global.css'-```+## General Changes -This double loading could occur since a `.css` file will be emitted and it's likely that the CSS string will also be used by the application code — for example, injected by the framework runtime. From Vite 4, the `.css` default export [has been deprecated](https://github.com/vitejs/vite/issues/11094). The `?inline` query suffix modifier needs to be used in this case, as that doesn't emit the imported `.css` styles.+### Allow path containing `.` to fallback to index.html -```ts-import stuff from './global.css?inline'-```+In Vite 4, accessing a path containing `.` did not fallback to index.html even if `appType` is set to `'SPA'` (default).+From Vite 5, it will fallback to index.html. -### Production Builds by Default+Note that the browser will no longer show the 404 error message in the console if you point the image path to a non-existent file (e.g. `<img src="./file-does-not-exist.png">`). -`vite build` will now always build for production regardless of the `--mode` passed. Previously, changing `mode` to other than `production` would result in a development build. If you wish to still build for development, you can set `NODE_ENV=development` in the `.env.{mode}` file.+### Manifest files are now generated in `.vite` directory by default -In part of this change, `vite dev` and `vite build` will not override `process.env.NODE_ENV` anymore if it is already defined. So if you've set `process.env.NODE_ENV = 'development'` before building, it will also build for development. This gives more control when running multiple builds or dev servers in parallel.+In Vite 4, the manifest files (`build.manifest`, `build.ssrManifest`) was generated in the root of `build.outDir` by default. From Vite 5, those will be generated in the `.vite` directory in the `build.outDir` by default. -See the updated [`mode` documentation](https://vitejs.dev/guide/env-and-mode.html#modes) for more details.+### CLI shortcuts require an additional `Enter` press -### Environment Variables+CLI shortcuts, like `r` to restart the dev server, now require an additional `Enter` press to trigger the shortcut. For example, `r + Enter` to restart the dev server. -Vite now uses `dotenv` 16 and `dotenv-expand` 9 (previously `dotenv` 14 and `dotenv-expand` 5). If you have a value including `#` or `` ` ``, you will need to wrap them with quotes.+This change prevents Vite from swallowing and controlling OS-specific shortcuts, allowing better compatibility when combining the Vite dev server with other processes, and avoids the [previous caveats](https://github.com/vitejs/vite/pull/14342). -```diff--VITE_APP=ab#cd`ef-+VITE_APP="ab#cd`ef"-```+## Removed Deprecated APIs -For more details, see the [`dotenv`](https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md) and [`dotenv-expand` changelog](https://github.com/motdotla/dotenv-expand/blob/master/CHANGELOG.md).+- Default exports of CSS files (e.g `import style from './foo.css'`): Use the `?inline` query instead+- `import.meta.globEager`: Use `import.meta.glob('*', { eager: true })` instead+- `ssr.format: 'cjs`' and `legacy.buildSsrCjsExternalHeuristics`