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.

Sign up for GitHub

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

Jump to bottom

Update dependency vue to v3 #205

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dependency vue to v3 #205

wants to merge 1 commit into from
+1 −1

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 14, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vue (source) 2.7.16 -> 3.4.27 age adoption passing confidence

Release Notes

vuejs/core (vue)

v3.4.27

Compare Source

Bug Fixes

v3.4.26

Compare Source

Bug Fixes

v3.4.25

Compare Source

Bug Fixes

v3.4.24

Compare Source

Bug Fixes

v3.4.23

Compare Source

Bug Fixes
  • runtime-core: fix regression for $attrs tracking in slots (6930e60), closes #​10710
  • runtime-core: use same internal object mechanism for slots (6df53d8), closes #​10709

v3.4.22

Compare Source

Bug Fixes
Performance Improvements
  • add __NO_SIDE_EFFECTS__ comments (#​9053) (d46df6b)
  • optimize component props/slots internal object checks (6af733d)
  • ssr: avoid calling markRaw on component instance proxy (4bc9f39)
  • ssr: optimize setup context creation for ssr in v8 (ca84316)

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
  • compat: correct enum value for COMPILER_FILTERS feature (#​9875) (77d33e2)
  • defineModel: always default modifiers to empty object (9bc3c7e), closes #​9945
  • defineModel: support local mutation when only prop but no listener is passed (97ce041)
  • types: fix defineModel watch type error (#​9942) (4af8583), closes #​9939
Features

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

Configuration

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

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ 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 added the dependencies Updates to dependencies label Jun 14, 2023
@renovate renovate bot requested a review from sgarner June 14, 2023 15:53
@renovate
Copy link
Contributor Author

renovate bot commented Jun 14, 2023 •
edited

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: vue-apollo-smart-ops@0.2.0-beta.1
npm error Found: eslint@9.0.0
npm error node_modules/eslint
npm error   dev eslint@"9.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/parser@7.5.0
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.5.0" from the root project
npm error   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/eslint-plugin@7.5.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.5.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-02T11_22_23_767Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-02T11_22_23_767Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch from 1c26362 to 46cc0dc Compare September 15, 2023 16:16
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 4 times, most recently from 2300fe7 to f79e093 Compare October 28, 2023 01:35
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch from f79e093 to c8468f8 Compare November 9, 2023 12:18
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch from c8468f8 to 5ede388 Compare November 28, 2023 11:17
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 2 times, most recently from 77471c7 to 451e94f Compare December 11, 2023 06:57
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 2 times, most recently from 3759889 to 39fa196 Compare December 22, 2023 12:28
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 6 times, most recently from a8c0ef5 to 8681758 Compare January 7, 2024 13:14
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 8 times, most recently from 128c67e to d928d2a Compare January 16, 2024 09:57
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 2 times, most recently from b88c3ae to e199dfa Compare January 21, 2024 16:18
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 5 times, most recently from cc3f3b3 to f6d1caf Compare February 17, 2024 21:43
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 2 times, most recently from 3b4d57a to 4dad145 Compare March 2, 2024 13:05
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 2 times, most recently from 25d114c to 19d2a43 Compare March 20, 2024 20:32
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 3 times, most recently from 3421533 to 2d67509 Compare April 25, 2024 15:43
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch 2 times, most recently from 95c18b9 to 1829bdc Compare May 2, 2024 11:22
@renovate renovate bot force-pushed the renovate/major-vue-monorepo branch from 1829bdc to c61841c Compare May 10, 2024 00:03
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 10, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: vue-apollo-smart-ops@0.2.0-beta.1
npm error Found: eslint@9.0.0
npm error node_modules/eslint
npm error   dev eslint@"9.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/parser@7.5.0
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.5.0" from the root project
npm error   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/eslint-plugin@7.5.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.5.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-10T00_03_02_291Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-10T00_03_02_291Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sgarner sgarner Awaiting requested review from sgarner

Assignees
No one assigned
Labels
dependencies Updates to dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants