From a9e561b169d6721d3047a1f6276ff35dc35cc22f Mon Sep 17 00:00:00 2001 From: Ghayth BenAbid Date: Sat, 19 Sep 2026 16:13:18 +0200 Subject: [PATCH] docs: clarify effective defaults for build.rolldownOptions.preserveEntrySignatures Vite overrides Rolldown's default 'exports-only' with false (client), 'strict' (lib), and 'allow-extension' (SSR). Document the effective Vite defaults so users know to set the option explicitly when needed. Fixes #23451 --- docs/config/build-options.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/config/build-options.md b/docs/config/build-options.md index 40049e20f5385a..20b8ac41c2f200 100644 --- a/docs/config/build-options.md +++ b/docs/config/build-options.md @@ -168,6 +168,8 @@ Directly customize the underlying Rolldown bundle. This is the same as options t Instead of `build.rolldownOptions.input`, it is recommended to set the top-level [`input`](/config/shared-options#input) option, because it will be used in dev as well. If `build.rolldownOptions.input` is set, it overrides the top-level `input` option for build only. +Note that Vite overrides `preserveEntrySignatures` by default: `false` for a regular client build, `'strict'` for library mode, and `'allow-extension'` for SSR builds. Set `build.rolldownOptions.preserveEntrySignatures` explicitly (e.g. `'exports-only'`) if you need Rolldown's default behavior. + ## build.rollupOptions - **Type:** `RolldownOptions`