-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update vue monorepo to v2.7.16 #317
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/vue-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
4 times, most recently
from
July 4, 2022 11:24
8438ce8
to
367fd5f
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo to v2.7.0
fix(deps): update vue monorepo to v2.7.1
Jul 4, 2022
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
2 times, most recently
from
July 5, 2022 03:03
89c40e2
to
956bf1c
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo to v2.7.1
fix(deps): update vue monorepo
Jul 5, 2022
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
from
July 5, 2022 04:40
956bf1c
to
2d7288e
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo
fix(deps): update vue monorepo to v2.7.2
Jul 5, 2022
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
from
July 6, 2022 11:24
2d7288e
to
a9424ae
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo to v2.7.2
fix(deps): update vue monorepo to v2.7.3
Jul 6, 2022
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
2 times, most recently
from
July 8, 2022 05:33
37dc451
to
7dc18d5
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo to v2.7.3
fix(deps): update vue monorepo to v2.7.4
Jul 8, 2022
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
4 times, most recently
from
July 13, 2022 03:56
402ea00
to
c1f676f
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo to v2.7.4
fix(deps): update vue monorepo to v2.7.5
Jul 13, 2022
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
from
July 15, 2022 11:42
c1f676f
to
a052ec3
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo to v2.7.5
fix(deps): update vue monorepo to v2.7.6
Jul 15, 2022
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
from
July 16, 2022 15:37
a052ec3
to
def703d
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo to v2.7.6
fix(deps): update vue monorepo to v2.7.7
Jul 16, 2022
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
3 times, most recently
from
July 18, 2022 20:51
52cd512
to
a41d46a
Compare
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
3 times, most recently
from
October 14, 2023 18:48
25bc8c1
to
22c5920
Compare
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
from
October 23, 2023 08:48
22c5920
to
6e8806f
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo to v2.7.14
fix(deps): update vue monorepo to v2.7.15
Oct 23, 2023
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
from
December 24, 2023 20:12
6e8806f
to
8102dba
Compare
renovate
bot
changed the title
fix(deps): update vue monorepo to v2.7.15
fix(deps): update vue monorepo to v2.7.16
Dec 24, 2023
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
8 times, most recently
from
March 9, 2024 12:07
f48e866
to
53d136f
Compare
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
6 times, most recently
from
August 31, 2024 12:23
dd65356
to
ecc653e
Compare
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
4 times, most recently
from
October 6, 2024 07:24
a0aeb15
to
20aac70
Compare
renovate
bot
force-pushed
the
renovate/vue-monorepo
branch
from
December 19, 2024 13:35
20aac70
to
75a3109
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
2.6.14
->2.7.16
2.6.14
->2.7.16
Release Notes
vuejs/vue (vue-template-compiler)
v2.7.16
Compare Source
Bug Fixes
v2.7.15
Compare Source
Bug Fixes
defineProps
statement (#12879) (51fef2c)v-on
(#12862) (b8c8b3f)withDefaults
(#12872) (099401e)v2.7.14
Compare Source
Bug Fixes
EventHandlers
(#12840) (0b3cf7d), closes #12832v2.7.13
Compare Source
Bug Fixes
v2.7.12
Compare Source
Reverts
v2.7.11
Compare Source
Bug Fixes
Performance Improvements
v2.7.10
Compare Source
Bug Fixes
v2.7.9
Compare Source
Bug Fixes
Features
v2.7.8
Compare Source
Bug Fixes
<script setup>
component resolution edge case with v3 (#12687) (a695c5a), closes #12685defineAsyncComponent
type (#12684) (ba7dd2c)Features
useListeners()
helper (adf3ac8)v2.7.7
Compare Source
Bug Fixes
v2.7.6
Compare Source
Bug Fixes
v2.7.5
Compare Source
Bug Fixes
vue.runtime.mjs
(#12648) (08fb4a2)v2.7.4
Compare Source
Bug Fixes
Features
v2.7.3
Compare Source
Bug Fixes
v2.7.2
Compare Source
Bug Fixes
Features
v2.7.1
Compare Source
Bug Fixes
v2.7.0
Compare Source
Backported Features
<script setup>
In addition, the following APIs are also supported:
defineComponent()
with improved type inference (compared toVue.extend
)h()
,useSlot()
,useAttrs()
,useCssModules()
set()
,del()
andnextTick()
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):
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()
, andshallowReactive()
will directly convert original objects instead of creating proxies. This means: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)await
in<script setup>
(Vue 2 does not support async component initialization)expose
option is not supported for options components (butdefineExpose()
is supported in<script setup>
).TypeScript Changes
defineComponent
provides improved type inference similar to that of Vue 3. Note the type ofthis
insidedefineComponent()
is not interoperable withthis
fromVue.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
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 v5Upgrade
vue
to^2.7.0
. You can also removevue-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.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.If you were previously using
@vue/composition-api
, update imports from it tovue
instead. Note that some APIs exported by the plugin, e.g.createApp
, are not ported in 2.7.Update
eslint-plugin-vue
to latest version (9+) if you run into unused variable lint errors when using<script setup>
.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 intsconfig.json
: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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.