docs(config): document preserveEntrySignatures defaults (fix #23451) - #23469
Open
koriyoshi2041 wants to merge 1 commit into
Open
docs(config): document preserveEntrySignatures defaults (fix #23451)#23469koriyoshi2041 wants to merge 1 commit into
koriyoshi2041 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Rolldown documents
preserveEntrySignatureswith a default of'exports-only', but Vite supplies different defaults based on the build mode. This makes the effective behavior unclear when the option is omitted.Fix
Document Vite's effective defaults under
build.rolldownOptions:falsefor regular client builds,'strict'for library builds, and'allow-extension'for SSR builds.Fixes #23451.
Test
pnpm exec oxfmt --check docs/config/build-options.mdpnpm run buildpnpm run docs-buildgit diff --checkRisk
Documentation-only. The values are taken directly from the current build option construction, and user-provided
rolldownOptionscontinue to override them.