fix(runtime-core): use feature flag for call to resolveMergedOptions
#12163
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.
Not sure whether this counts as
fix
,perf
orrefactor
. Feel free to adjust accordingly.I was doing some analysis of bundle size across Vue versions and noticed a jump in 3.2.39. This seems to have been caused by #6250. We didn't have size checks on PRs back then, and I don't see it discussed on the PR, so I assume this just slipped through.
It only impacts projects using
__VUE_OPTIONS_API__: false
.The call to
resolveMergedOptions
prevents a big chunk of the Options API from being treeshaken. It's used to resolvetemplate
fromextends
andmixins
, but I believe that is only relevant when__FEATURE_OPTIONS_API__
istrue
.