Skip to content

Update vue monorepo

renovate-bot requested to merge renovate/vue-monorepo into develop

This MR contains the following updates:

Package Type Update Change
@vue/compiler-sfc devDependencies patch ^3.1.0 -> 3.2.37
vue dependencies patch ^3.2.31 -> 3.2.37
vue-style-loader devDependencies patch 4.1.2 -> 4.1.3
vue-template-compiler dependencies minor 2.6.11 -> 2.7.8

Release Notes

vuejs/core

v3.2.37

Compare Source

Bug Fixes

v3.2.36

Compare Source

Bug Fixes
Performance Improvements

v3.2.35

Compare Source

Bug Fixes

v3.2.34

Compare Source

Bug Fixes
  • compiler-core: should generate HYDRATE_EVENTS flag on dynamic component that resolves to element (415091b), closes #​5870
  • compiler-sfc: support export { default } from '...' (#​5937) (73e6523), closes #​5935
  • compiler-sfc: type-only defineProps does not recognize Promise (fix #​5941) (#​5943) (991d623)
  • compiler-ssr: fix component event handlers inheritance in ssr (f811dc2), closes #​5664
  • compiler-ssr: fix wrong attrs fallthrough on non-single-root v-if branches (516bc54), closes #​5140
  • compiler-ssr: only inject fallthrough attrs for root transition/keep-alive (c65b805)
  • keep-alive: fix keep-alive rendering when placed in vnode branch (0841b9b), closes #​4817
  • runtime-core: adjust force diff of dev root fragments (cdda49b), closes #​5946
  • ssr/teleport: support nested teleports in ssr (595263c), closes #​5242
  • ssr: fix hydration error on falsy v-if inside transition/keep-alive (ee4186e), closes #​5352
  • ssr: fix hydration error when teleport is used as component root (b60cff0), closes #​4293
  • ssr: fix hydration error when transition contains comment children (3705b3b), closes #​5351
  • ssr: fix hydration for slot with empty text node (939209c), closes #​5728
  • ssr: fix hydration mismatch caused by multi-line comments inside slot (e1bc268), closes #​5355
  • ssr: inherit scope id on functional component during ssr (847d7f7), closes #​5817
  • ssr: render fallthrough attributes for transition-group with tag (aed10c5), closes #​5141
  • ssr: support client-compiled v-model with dynamic type during ssr (#​5787) (c03459b), closes #​5786
  • types: export ComponentProvideOptions (#​5947) (3e2850f)
  • types: fix defineComponent inference to Component (#​5949) (7c8f457)

v3.2.33

Compare Source

Bug Fixes

v3.2.32

Compare Source

Bug Fixes
vuejs/vue-style-loader

v4.1.3

Compare Source

Bug Fixes
  • also support passed ES modules from css-loader in addition to CommonJS format (#​47) (8b584bd)
  • es module interop in HMR code (8bc2fe3)
vuejs/vue

v2.7.8

Compare Source

Bug Fixes
Features
  • setup: support listeners on setup context + useListeners() helper (adf3ac8)

v2.7.7

Compare Source

Bug Fixes
  • codegen: script setup should not attempt to resolve native elements as component (e8d3a7d), closes #​12674
  • inject: fix edge case of provided with async-mutated getters (ea5d0f3), closes #​12667
  • setup: ensure setup context slots can be accessed immediately (67760f8), closes #​12672
  • types: vue.d.ts should use relative import to v3-component-public-instance (#​12668) (46ec648), closes #​12666
  • watch: fix queueing multiple post watchers (25ffdb6), closes #​12664

v2.7.6

Compare Source

Bug Fixes

v2.7.5

Compare Source

Bug Fixes
  • add missing export from vue.runtime.mjs (#​12648) (08fb4a2)
  • detect property add/deletion on reactive objects from setup when used in templates (a6e7498)
  • do not set currentInstance in beforeCreate (0825d30), closes #​12636
  • reactivity: fix watch behavior inconsistency + deep ref shallow check (98fb01c), closes #​12643
  • sfc: fix sfc name inference type check (04b4703), closes #​12637
  • types: support Vue interface augmentations in defineComponent (005e52d), closes #​12642
  • watch: fix deep watch for structures containing raw refs (1a2c3c2), closes #​12652

v2.7.4

Compare Source

Bug Fixes
  • build: fix mjs dual package hazard (012e10c), closes #​12626
  • compiler-sfc: use safer deindent default for compatibility with previous behavior (b70a258)
  • pass element creation helper to static render fns for functional components (dc8a68e), closes #​12625
  • ssr/reactivity: fix array setting error at created in ssr [#​12632] (#​12633) (ca7daef)
  • types: fix missing instance properties on defineComponent this (f8de4ca), closes #​12628
  • types: fix this.$slots type for defineComponent (d3add06)
  • types: fix type inference when using components option (1d5a411)
  • types: global component registration type compat w/ defineComponent (26ff4bc), closes #​12622
  • watch: fix watchers triggered in mounted hook (8904ca7), closes #​12624
Features

v2.7.3

Compare Source

Bug Fixes

v2.7.2

Compare Source

Bug Fixes
  • compiler-sfc: preserve old deindent behavior for pug (1294385), closes #​12611
Features

v2.7.1

Compare Source

Bug Fixes

v2.7.0

Compare Source

Backported Features

In addition, the following APIs are also supported:

  • defineComponent() with improved type inference (compared to Vue.extend)

  • h(), useSlot(), useAttrs(), useCssModules()

  • set(), del() and nextTick() are also provided as named exports in ESM builds.

  • The emits option is also supported, but only for type-checking purposes (does not affect runtime behavior)

    2.7 also supports using ESNext syntax in template expressions. When using a build system, the compiled template render function will go through the same loaders / plugins configured for normal JavaScript. This means if you have configured Babel for .js files, it will also apply to the expressions in your SFC templates.

Notes on API exposure

  • In ESM builds, these APIs are provided as named exports (and named exports only):

    import Vue, { ref } from 'vue'

Vue.ref // undefined, use named export instead

  • In UMD and CJS builds, these APIs are exposed as properties on the global Vue object.

  • When bundling with CJS builds externalized, bundlers should be able to handle ESM interop when externalizing CJS builds.

Behavior Differences from Vue 3

The Composition API is backported using Vue 2's getter/setter-based reactivity system to ensure browser compatibility. This means there are some important behavior differences from Vue 3's proxy-based system:

  • All Vue 2 change detection caveats still apply.

  • reactive(), ref(), and shallowReactive() will directly convert original objects instead of creating proxies. This means:

    // true in 2.7, false in 3.x
reactive(foo) === foo

  • readonly() does create a separate object, but it won't track newly added properties and does not work on arrays.

  • Avoid using arrays as root values in reactive() because without property access the array's mutation won't be tracked (this will result in a warning).

  • Reactivity APIs ignore properties with symbol keys.

In addition, the following features are explicitly NOT ported:

  • ❌ createApp() (Vue 2 doesn't have isolated app scope)
  • ❌ Top-level await in <script setup> (Vue 2 does not support async component initialization)
  • ❌ TypeScript syntax in template expressions (incompatible w/ Vue 2 parser)
  • ❌ Reactivity transform (still experimental)
  • ❌ expose option is not supported for options components (but defineExpose() is supported in <script setup>).
TypeScript Changes

  • defineComponent provides improved type inference similar to that of Vue 3. Note the type of this inside defineComponent() is not interoperable with this from Vue.extend().

  • Similar to Vue 3, TSX support is now built-in. If your project previously had manual JSX type shims, make sure to remove them.

Upgrade Guide

Vue CLI / webpack

  1. Upgrade local @vue/cli-xxx dependencies the latest version in your major version range (if applicable):

    • ~4.5.18 for v4
    • ~5.0.6 for v5

  2. Upgrade vue to ^2.7.0. You can also remove vue-template-compiler from the dependencies - it is no longer needed in 2.7.

    Note: if you are using @vue/test-utils, you may need to keep it in the dependencies for now, but this requirement will also be lifted in a new release of test utils.

  3. Check your package manager lockfile to ensure the following dependencies meet the version requirements. They may be transitive dependencies not listed in package.json.

    • vue-loader: ^15.10.0
    • vue-demi: ^0.13.1

    If not, you will need to remove node_modules and the lockfile and perform a fresh install to ensure they are bumped to the latest version.

  4. If you were previously using @vue/composition-api, update imports from it to vue instead. Note that some APIs exported by the plugin, e.g. createApp, are not ported in 2.7.

  5. Update eslint-plugin-vue to latest version (9+) if you run into unused variable lint errors when using <script setup>.

  6. The SFC compiler for 2.7 now uses PostCSS 8 (upgraded from 7). PostCSS 8 should be backwards compatible with most plugins, but the upgrade may cause issues if you were previously using a custom PostCSS plugin that can only work with PostCSS 7. In such cases, you will need to upgrade the relevant plugins to their PostCSS 8 compatible versions.

Vite

2.7 support for Vite is provided via a new plugin: @​vitejs/plugin-vue2. This new plugin requires Vue 2.7 or above and supersedes the existing vite-plugin-vue2.

Note that the new plugin does not handle Vue-specific JSX / TSX transform, which is intentional. Vue 2 JSX / TSX transform should be handled in a separate, dedicated plugin, which will be provided soon.

Volar Compatibility

2.7 ships improved type definitions so it is no longer necessary to install @vue/runtime-dom just for Volar template type inference support. All you need now is the following config in tsconfig.json:

{
  // ...
  "vueCompilerOptions": {
    "target": 2.7
  }
}
Devtools Support

Vue Devtools 6.2.0 has added support for inspecting 2.7 Composition API state, but the extensions may still need a few days to go through review on respective publishing platforms.

Bug Fixes
  • sfc: only include legacy decorator parser plugin when new plugin is not used (326d24a)

v2.6.14

Compare Source

Bug Fixes
Features

v2.6.13

Compare Source

Bug Fixes
Features
Performance Improvements

v2.6.12

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this MR, click this checkbox.

This MR has been generated by Renovate Bot.

Edited by renovate-bot

Merge request reports