vue-template-compiler - npm Package Versions

2.7.0-alpha.9 (2022-06-16)

Features

• defineExpose() support (3c2707b)
• directive resolution for <script setup> (aa2b1f4)
• resolve components from <script setup> (4b19339)
• types for <script setup> macros (7173ad4)

2.7.0-alpha.8 (2022-06-14)

Features

• Basic <script setup> support. Requires vue-loader@^15.10.0-beta.1.
  • Component resolution doesn't work yet
  • Types for defineXXX macros not supported yet

2.7.0-alpha.7 (2022-06-14)

2.7.0-alpha.6 (2022-06-09)

Features

• Add JSX types for Volar integration. No longer requires @vue/runtime-dom for component props validation in templates.

2.7.0-alpha.5 (2022-06-06)

Bug Fixes

• fix scopedSlots regression (4f2a04e)

2.7.0-alpha.4 (2022-06-01)

Bug Fixes

• guard against non-object provide value (c319cc7)

Features

• defineComponent 206f8a7f

2.7.0-alpha.3 (2022-06-01)

2.7.0-alpha.2 (2022-06-01)

Features

• add exports field + mjs build (d317237)
• expose set/del as named exports (5673363)

2.7.0-alpha.1 (2022-05-31)

This release includes full Composition API support, including:

• setup() support in components
• Reactivity APIs (ref(), reactive() etc.)
• Lifecycle hooks (onMounted() etc.)
• provide() and inject()
• useSlots() and useAttrs()
• template refs with setup()

Behavior difference from Vue 3

• The reactivity system is still getter/setter based and does not use Proxies, so all Vue 2 change detection caveats still apply.
• reactive(), ref(), and shallowReactive() will directly convert original objects instead of creating proxies. They also do not convert properties with symbol keys.
• 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).
• readonly() does create a separate object, but it won't track newly added properties and does not work on arrays.

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
  

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

• In UMD builds, these APIs are exposed on the global Vue object.

In addition:

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

Bug Fixes

• v-on: add removing all dom event listeners when vnode destroyed (#10085) (3d29ba8)

Features

• compiler: condenses staticClass whitespace (fix #12113) (#12195) (515467a)

2.6.14 (2021-06-07)

Bug Fixes

• types: async Component types (#11906) (c52427b)
• v-slot: fix scoped slot normalization combined with v-if (#12104) (38f71de)

Features

• ssr: vue-ssr-webpack-plugin compatible with webpack 5 (#12002) (80e7730)