Skip to content
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

chore(deps): update dependency @vue/runtime-dom to v3.4.21 - autoclosed #748

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vue/runtime-dom (source) 3.2.39 -> 3.4.21 age adoption passing confidence

Release Notes

vuejs/core (@​vue/runtime-dom)

v3.4.21

Compare Source

Bug Fixes

v3.4.20

Compare Source

Bug Fixes

v3.4.19

Compare Source

Bug Fixes
Features

Note: this warning is categorized as a feature but released in a patch because it does not affect public APIs.

Performance Improvements

v3.4.18

Compare Source

Bug Fixes

v3.4.17

Compare Source

Reverts

v3.4.16

Compare Source

Bug Fixes
Reverts

v3.4.15

Compare Source

Bug Fixes
  • compiler-sfc: fix type resolution for symlinked node_modules structure w/ pnpm (75e866b), closes #​10121
  • correct url for production error reference links (c3087ff)
  • hydration: fix incorect mismatch warning for option with non-string value and inner text (d16a213)
  • reactivity: re-fix #​10114 (#​10123) (c2b274a)
  • runtime-core: should not warn out-of-render slot fn usage when mounting another app in setup (#​10125) (6fa33e6), closes #​10124
Performance Improvements
  • templateRef: avoid double render when using template ref on v-for (de4d2e2), closes #​9908
  • v-model: optimize v-model multiple select w/ large lists (2ffb956), closes #​10014

v3.4.14

Compare Source

Bug Fixes

v3.4.13

Compare Source

Bug Fixes

v3.4.12

Compare Source

Reverts

v3.4.11

Compare Source

Bug Fixes

v3.4.10

Compare Source

Bug Fixes
  • hydration: should not warn on falsy bindings of non-property keys (3907c87)

v3.4.9

Compare Source

Bug Fixes
  • build: avoid accessing FEATURE_PROD_DEVTOOLS flag in root scope (dfd9654)
  • hydration: do not warn against bindings w/ object values (dcc68ef)
  • runtime-dom: unify behavior for v-show + style display binding (#​10075) (cd419ae), closes #​10074
  • suspense: avoid double-patching nested suspense when parent suspense is not resolved (#​10055) (bcda96b), closes #​8678

v3.4.8

Compare Source

Bug Fixes

v3.4.7

Compare Source

Bug Fixes
Reverts
  • "dx(computed): warn incorrect use of getCurrentInstance inside computed" (2fd3905)

v3.4.6

Compare Source

Bug Fixes

v3.4.5

Compare Source

Bug Fixes
  • compiler-sfc: fix co-usage of defineModel transform options and props destructure (b20350d), closes #​9972
  • compiler-sfc: fix sfc template unref rewrite for class instantiation (ae60a91), closes #​6483 #​6491
  • compiler-ssr: fix node clone edge case caused by AST reuse (#​9983) (7dbdb3e), closes #​9981
  • watch: cleanup watcher effect from scope when manually stopped (#​9978) (d2d8955)

v3.4.4

Compare Source

Bug Fixes
  • compiler-sfc: fix scss source map regression (71d3121), closes #​9970 #​9969
  • compiler-sfc: use compilerOptions when re-parsing consumed AST (d94d8d4)
  • defineModel: support kebab-case/camelCase mismatches (#​9950) (10ccb9b)
  • runtime-core: correctly assign suspenseId to avoid conflicts with the default id (#​9966) (0648804), closes #​9944
  • ssr: avoid rendering transition-group slot content as a fragment (#​9961) (0160264), closes #​9933
  • watch: remove instance unmounted short circuit in getter of watchEffect (#​9948) (f300a40)
  • watch: revert watch behavior when watching shallow reactive objects (a9f781a), closes #​9965
Performance Improvements
  • watch: avoid double traverse for reactive source (24d77c2)

v3.4.3

Compare Source

Bug Fixes
  • compiler-sfc: respect sfc parse options in cache key (b8d58ec)

v3.4.2

Compare Source

Bug Fixes

v3.4.1

Compare Source

Bug Fixes
Features

Note: this warning is categorized as a feature but released in a patch because it does not affect public APIs.

Performance Improvements

v3.4.0

Compare Source

Read this blog post for an overview of the release highlights.

Potential Actions Needed
  1. To fully leverage new features in 3.4, it is recommended to also update the following dependencies when upgrading to 3.4:

    • Volar / vue-tsc@^1.8.27 (required)
    • @​vitejs/plugin-vue@​^5.0.0 (if using Vite)
    • nuxt@^3.9.0 (if using Nuxt)
    • vue-loader@^17.4.0 (if using webpack or vue-cli)
  2. If using TSX with Vue, check actions needed in Removed: Global JSX Namespace.

  3. Make sure you are no longer using any deprecated features (if you are, you should have warnings in the console telling you so). They may have been removed in 3.4.

Features
Performance Improvements
  • compiler-sfc: avoid sfc source map unnecessary serialization and parsing (f15d2f6)
  • compiler-sfc: remove magic-string trim on script (e8e3ec6)
  • compiler-sfc: use faster source map addMapping (50cde7c)
  • compiler-core: optimize away isBuiltInType (66c0ed0)
  • compiler-core: optimize position cloning (2073236)
  • codegen: optimize line / column calculation during codegen (3be53d9)
  • codegen: optimize source map generation (c11002f)
  • shared: optimize makeMap (ae6fba9)
BREAKING CHANGES
Global JSX Registration Removed

Starting in 3.4, Vue no longer registers the global JSX namespace by default. This is necessary to avoid global namespace collision with React so that TSX of both libs can co-exist in the same project. This should not affect SFC-only users with latest version of Volar.

If you are using TSX, there are two options:

  1. Explicitly set jsxImportSource to 'vue' in tsconfig.json before upgrading to 3.4. You can also opt-in per file by adding a /* @​jsxImportSource vue */ comment at the top of the file.

  2. If you have code that depends on the presence of the global JSX namespace, e.g. usage of types like JSX.Element etc., you can retain the exact pre-3.4 global behavior by explicitly referencing vue/jsx, which registers the global JSX namespace.

Note that this is a type-only breaking change in a minor release, which adheres to our release policy.

Deprecated Features Removed
  • Reactivity Transform was marked deprecated in 3.3 and is now removed in 3.4. This change does not require a major due to the feature being experimental. Users who wish to continue using the feature can do so via the Vue Macros plugin.
  • app.config.unwrapInjectedRef has been removed. It was deprecated and enabled by default in 3.3. In 3.4 it is no longer possible to disable this behavior.
  • @vnodeXXX event listeners in templates are now a compiler error instead of a deprecation warning. Use @vue:XXX listeners instead.
  • v-is directive has been removed. It was deprecated in 3.3. Use the is attribute with vue: prefix instead.

v3.3.13

Compare Source

Bug Fixes

v3.3.12

Compare Source

Bug Fixes

v3.3.11

Compare Source

Bug Fixes

v3.3.10

Compare Source

Bug Fixes
Performance Improvements
  • optimize on* prop check (38aaa8c)
  • runtime-dom: cache modifier wrapper functions (da4a4fb), closes #​8882
  • v-on: constant handlers with modifiers should not be treated as dynamic (4d94ebf)

v3.3.9

Compare Source

Bug Fixes

v3.3.8

Compare Source

Bug Fixes

v3.3.7

Compare Source

Please refer to CHANGELOG.md for details.

v3.3.6

Compare Source

Please refer to CHANGELOG.md for details.

v3.3.5

Compare Source

Please refer to CHANGELOG.md for details.

v3.3.4

Compare Source

Please refer to CHANGELOG.md for details.

v3.3.3

Compare Source

Please refer to CHANGELOG.md for details.

v3.3.2

Compare Source

Please refer to [CHANGELOG.md](https://


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 PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/vue-runtime-dom-3.x-lockfile branch from b89530e to a06d592 Compare February 8, 2024 05:15
@renovate renovate bot changed the title chore(deps): update dependency @vue/runtime-dom to v3.4.15 chore(deps): update dependency @vue/runtime-dom to v3.4.16 Feb 8, 2024
@renovate renovate bot force-pushed the renovate/vue-runtime-dom-3.x-lockfile branch from a06d592 to a5c4746 Compare February 9, 2024 05:29
@renovate renovate bot changed the title chore(deps): update dependency @vue/runtime-dom to v3.4.16 chore(deps): update dependency @vue/runtime-dom to v3.4.18 Feb 9, 2024
@renovate renovate bot force-pushed the renovate/vue-runtime-dom-3.x-lockfile branch from a5c4746 to 20b0019 Compare February 14, 2024 05:47
@renovate renovate bot changed the title chore(deps): update dependency @vue/runtime-dom to v3.4.18 chore(deps): update dependency @vue/runtime-dom to v3.4.19 Feb 14, 2024
@renovate renovate bot force-pushed the renovate/vue-runtime-dom-3.x-lockfile branch from 20b0019 to 23d6f92 Compare February 26, 2024 04:54
@renovate renovate bot changed the title chore(deps): update dependency @vue/runtime-dom to v3.4.19 chore(deps): update dependency @vue/runtime-dom to v3.4.20 Feb 26, 2024
@renovate renovate bot force-pushed the renovate/vue-runtime-dom-3.x-lockfile branch from 23d6f92 to cfa7b3c Compare February 29, 2024 02:47
@renovate renovate bot changed the title chore(deps): update dependency @vue/runtime-dom to v3.4.20 chore(deps): update dependency @vue/runtime-dom to v3.4.21 Feb 29, 2024
@renovate renovate bot changed the title chore(deps): update dependency @vue/runtime-dom to v3.4.21 chore(deps): update dependency @vue/runtime-dom to v3.4.21 - autoclosed Mar 24, 2024
@renovate renovate bot closed this Mar 24, 2024
@renovate renovate bot deleted the renovate/vue-runtime-dom-3.x-lockfile branch March 24, 2024 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants