chore(deps): bump vue and @vue/compiler-sfc

[dependabot]

Bumps vue and @vue/compiler-sfc. These dependencies needed to be updated together.
Updates vue from 3.0.5 to 3.1.1

Commits

• See full diff in compare view

Updates @vue/compiler-sfc from 3.0.5 to 3.1.1

Release notes

Sourced from @​vue/compiler-sfc's releases.

v3.1.1

Please refer to CHANGELOG.md for details.

v3.1.0 Pluto

Features

• Migration Build: a build of Vue 3 that provides Vue 2 compatible behavior. The Migration Build is intended to help migrating existing Vue 2 apps to Vue 3.
• compiler-core: whitespace handling strategy (dee3d6a)
• support component-level compilerOptions when using runtime compiler (ce0bbe0)
• config: support configuring runtime compiler via app.config.compilerOptions (091e6d6)
• support casting plain element to component via is="vue:xxx" (af9e699)
• devtools: improved KeepAlive support (03ae300)
• devtools: performance events (f7c54ca)
• onServerPrefetch (#3070) (349eb0f)

Performance Improvements

• only trigger $attrs update when it has actually changed (5566d39)
• compiler: skip unncessary checks when parsing end tag (048ac29)
• avoid deopt for props/emits normalization when global mixins are used (51d2be2)

Deprecations

• app.config.isCustomElement has been deprecated and should be now nested under app.config.compilerOptions. [Docs]
• delimiters component option has been deprecated and should now be nested under the compilerOptions component option. [Docs]
• v-is has been deprecated in favor of is="vue:xxx" [Docs]

Minor Breaking Changes

• this.$props and the props object passed to setup() 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:

  const isAbsent = Symbol()
  export default {
  props: {
  foo: { default: isAbsent }
  },
  setup(props) {
  if (props.foo === isAbsent) {
  // foo is absent
  }
  }
  }

• optionMergeStrategies functions 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

... (truncated)

Changelog

Sourced from @​vue/compiler-sfc's changelog.

3.1.1 (2021-06-07)

Bug Fixes

• compat: update cjs dist file names (#3893) (434ea30)

3.1.0 (2021-06-07)

Features

• Migration Build
• compiler-core: whitespace handling strategy (dee3d6a)
• support component-level compilerOptions when using runtime compiler (ce0bbe0)
• config: support configuring runtime compiler via app.config.compilerOptions (091e6d6)
• support casting plain element to component via is="vue:xxx" (af9e699)
• devtools: improved KeepAlive support (03ae300)
• devtools: performance events (f7c54ca)
• onServerPrefetch (#3070) (349eb0f)

Performance Improvements

• only trigger $attrs update when it has actually changed (5566d39)
• compiler: skip unncessary checks when parsing end tag (048ac29)
• avoid deopt for props/emits normalization when global mixins are used (51d2be2)

Deprecations

• app.config.isCustomElement has been deprecated and should be now nested under app.config.compilerOptions. [Docs]
• delimiters component option has been deprecated and should now be nested under the compilerOptions component option. [Docs]
• v-is has been deprecated in favor of is="vue:xxx" [Docs]

Minor Breaking Changes

• this.$props and the props object passed to setup() 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:

  const isAbsent = Symbol()
  export default {
  props: {
  foo: { default: isAbsent }
  },
  setup(props) {
  if (props.foo === isAbsent) {
  // foo is absent
  }

... (truncated)

Commits

• ade9bd9 release: v3.1.1
• ac15df4 release: v3.1.0
• 71f7c25 release: v3.1.0-beta.7
• 8b94464 fix(compiler-sfc): fix style injection when using normal script + setup
• 2c7bd42 fix(compiler-sfc): fix template expression assignment codegen for script setu...
• aa96a0e release: v3.1.0-beta.6
• 6bfb50a fix(compiler-sfc): correctly remove parens used for wrapping (#3582)
• f0eb197 release: v3.1.0-beta.5
• f1f5230 release: v3.1.0-beta.4
• 01e8ba8 fix(compiler-sfc): support tsx in setup script (#3825)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.