Skip to content

docs: clarify effective defaults for build.rolldownOptions.preserveEntrySignatures - #23524

Open
GhaythBenAbid wants to merge 1 commit into
vitejs:mainfrom
GhaythBenAbid:fix/vite-quick-win
Open

GhaythBenAbid wants to merge 1 commit into
vitejs:mainfrom
GhaythBenAbid:fix/vite-quick-win

Conversation

@GhaythBenAbid

Copy link
Copy Markdown

Fixes #23451

What changed:

  • Clarified in docs/config/build-options.md that Vite overrides preserveEntrySignatures with effective defaults (false for client, 'strict' for library, 'allow-extension' for SSR) instead of Rolldown's 'exports-only'.

Why:

  • Users expecting Rolldown's default were confused when exports were not preserved unless explicitly setting preserveEntrySignatures: 'exports-only'. Docs now make the override explicit and guide users to set it explicitly when needed.

Minimal docs-only change, no runtime code affected.

…trySignatures

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 vitejs#23451
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

build.rolldownOptions.preserveEntrySignatures shows incorrect default

2 participants