@vue/compiler-sfc
3.5.46 · 20 Nov 2026MIT36.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @vue/compiler-sfc From 3.0.11 to 3.1.0
1 release in betweenevery note read
- 5
- changes to make
- 0
- advisories fixed
- 11
- new
- 49
- fixes
Start here
Before you upgrade
Tick each one off as you go- Breaking3.1.0
- Breaking3.1.0
- Deprecated3.1.0
- Deprecated3.1.0
- Deprecated3.1.0
Release by release
- Breaking
this.$propsand thepropsobject passed tosetup()now always contain all the keys for declared props, even for props that are absent (4fe4de0). This has always been the behavior in Vue 2 and is therefore considered a fix (see reasoning in #3288). However, this could break Vue 3 code that relied on the keys for prop absence checks. The workaround is to use a Symbol default value for props that need absence checks: - Breaking
optionMergeStrategiesfunctions no longer receive the component instance as the 3rd argument. The argument was technically internal in Vue 2 and only used for generating warnings, and should not be needed in userland code. This removal enables much more efficient caching of option merging. - Deprecated
app.config.isCustomElementhas been deprecated and should be now nested underapp.config.compilerOptions. [Docs] - Deprecated
delimiterscomponent option has been deprecated and should now be nested under thecompilerOptionscomponent option. [Docs]
- Breaking
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.