Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
GhaythBenAbid wants to merge 1 commit into from
Closed

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/config/build-options.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Expand Down
Loading