Interface BuildEnvironmentOptions

Directory relative from outDir where the built js/css/image assets will be placed.

Static asset files smaller than this number (in bytes) will be inlined as base64 strings. If a callback is passed, a boolean can be returned to opt-in or opt-out of inlining. If nothing is returned the default logic applies.

Default limit is 4096 (4 KiB). Set to 0 to disable.

Adjust chunk size warning limit (in kB).

Options to pass on to @rollup/plugin-commonjs

Copy the public directory to outDir on write.

create the Build Environment instance

Whether to code-split CSS. When enabled, CSS in async chunks will be inlined as strings in the chunk and inserted via dynamically created style tags when the chunk is loaded.

Override CSS minification specifically instead of defaulting to build.minify, so you can configure minification for JS and CSS separately.

An optional separate target for CSS minification. As esbuild only supports configuring targets to mainstream browsers, users may need this option when they are targeting a niche browser that comes with most modern JavaScript features but has poor CSS support, e.g. Android WeChat WebView, which doesn't support the #RGBA syntax.

Options to pass on to @rollup/plugin-dynamic-import-vars

Emit assets during build. Frameworks can set environments.ssr.build.emitAssets By default, it is true for the client and false for other environments.

Empty outDir on write.

Build in library mode. The value should be the global name of the lib in UMD mode. This will produce esm + cjs + umd bundle formats with default configurations that are suitable for distributing libraries.

Whether to emit a .vite/license.md file that includes all bundled dependencies' licenses. Pass an object to customize the output file name.

Whether to emit a .vite/manifest.json in the output dir to map hash-less filenames to their hashed versions. Useful when you want to generate your own HTML instead of using the one generated by Vite.

Example:

{
  "main.js": {
    "file": "main.68fe3fad.js",
    "css": "main.e6b63442.css",
    "imports": [...],
    "dynamicImports": [...]
  }
}
Copy

Set to false to disable minification, or specify the minifier to use. Available options are 'terser' or 'esbuild'.

Configure module preload Note: does not apply to library mode.

Directory relative from root where build output will be placed. If the directory exists, it will be removed before the build.

whether to inject module preload polyfill. Note: does not apply to library mode.

Set to false to disable reporting compressed chunk sizes. Can slightly improve build speed.

Will be merged with internal rollup options. https://rollupjs.org/configuration-options/

If true, a separate sourcemap file will be created. If 'inline', the sourcemap will be appended to the resulting output file as data URI. 'hidden' works like true except that the corresponding sourcemap comments in the bundled files are suppressed.

Produce SSR oriented build. Note this requires specifying SSR entry via rollupOptions.input.

Emit assets during SSR.

Generate SSR manifest for determining style links and asset preload directives in production.

Compatibility transform target. The transform is performed with esbuild and the lowest supported target is es2015. Note this only handles syntax transformation and does not cover polyfills

Default: 'baseline-widely-available' - transpile targeting browsers that are included in the Baseline Widely Available on 2025-05-01. (Chrome 107+, Edge 107+, Firefox 104+, Safari 16+).

Another special value is 'esnext' - which only performs minimal transpiling (for minification compat).

For custom targets, see https://esbuild.github.io/api/#target and https://esbuild.github.io/content-types/#javascript for more details.

Options for terser https://terser.org/docs/api-reference#minify-options

In addition, you can also pass a maxWorkers: number option to specify the max number of workers to spawn. Defaults to the number of CPUs minus 1.

Rollup watch options https://rollupjs.org/configuration-options/#watch

Whether to write bundle to disk