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 @vitejs/plugin-vue to v5 #120

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 28, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitejs/plugin-vue (source) 2.3.4 -> 5.2.1 age adoption passing confidence

Release Notes

vitejs/vite-plugin-vue (@​vitejs/plugin-vue)

v5.2.1

v5.2.0

  • feat: add a feature option to support custom component id generator (#​461) (7a1fc4c), closes #​461

v5.1.5

v5.1.4

v5.1.3

v5.1.2

v5.1.1

  • fix(plugin-vue): clear script cache if recall (f5eb5ac), closes #​431

v5.1.0

v5.0.5

v5.0.4

v5.0.3

v5.0.2

  • fix: ensure consistent user template options when reusing AST (bc0ad64), closes #​322
  • fix: only enable ast reuse for vue 3.4.3+ (4a53b6f)
  • chore: bump vue to 3.4.2 (97002e1)

v5.0.1

v5.0.0

  • Breaking: drop reactivityTransform support
  • Breaking: drop Node 14/16 support
  • Breaking: drop Vite 4.x support
  • Vue 3.4 template AST reuse support
  • Vue 3.4 compile-time flag __VUE_PROD_HYDRATION_MISMATCH_DETAILS__ support
  • Added customElement option
  • Deprecated defineModel option

v4.5.0

v4.4.1

v4.4.0

v4.3.4

Compare Source

v4.3.3

Compare Source

v4.3.2

Compare Source

v4.3.1

Compare Source

  • fix: revert "fix(plugin-vue): distinguish HMR and transform descriptor (#​227)" (0c28448), closes #​227

v4.3.0

Compare Source

v4.2.3

Compare Source

  • fix(types): widen allowed script options for 3.3 features (3ac08e4)

v4.2.2

Compare Source

  • fix: ignore generic attribute when generating script import (3170af1)
  • chore: bump vite (ffe74e5)
  • chore: bump vue version (799d875)

v4.2.1

Compare Source

v4.2.0

Compare Source

  • feat: support 3.3 imported types in SFC macros (c891652)

v4.1.0

Compare Source

  • fix: avoid resolving to 2.7 compiler-sfc (cf36b3e)

v4.0.0

Compare Source

v3.2.0

Compare Source

v3.1.2

Compare Source

v3.1.1

Compare Source

v3.1.0

Compare Source

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source


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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Dec 28, 2023

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @dimensionalpocket/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vite
npm ERR!   dev vite@"2.9.15" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^5.0.0" from @vitejs/[email protected]
npm ERR! node_modules/@vitejs/plugin-vue
npm ERR!   dev @vitejs/plugin-vue@"5.0.4" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-02-12T19_36_34_426Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch 2 times, most recently from 60c70e2 to 3c0acb1 Compare January 2, 2024 17:13
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 3c0acb1 to 8cee5a9 Compare January 13, 2024 11:12
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 8cee5a9 to d0b94f9 Compare February 12, 2024 19:36
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from d0b94f9 to 27065d6 Compare June 3, 2024 08:53
Copy link
Contributor Author

renovate bot commented Jun 3, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @dimensionalpocket/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vite
npm ERR!   dev vite@"2.9.15" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^5.0.0 || ^6.0.0" from @vitejs/[email protected]
npm ERR! node_modules/@vitejs/plugin-vue
npm ERR!   dev @vitejs/plugin-vue@"5.2.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-12-09T06_04_44_113Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch 2 times, most recently from e1affe5 to a703578 Compare July 30, 2024 10:13
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from a703578 to d080e16 Compare August 4, 2024 15:30
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from d080e16 to 0d72fb7 Compare September 1, 2024 18:34
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 0d72fb7 to c651297 Compare September 21, 2024 02:22
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch 2 times, most recently from 93b41de to d89bae9 Compare November 16, 2024 13:04
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from d89bae9 to fdee626 Compare November 29, 2024 14:14
@renovate renovate bot changed the title chore(deps): update dependency @vitejs/plugin-vue to v5 chore(deps): update dependency @vitejs/plugin-vue to v5 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/vitejs-plugin-vue-5.x branch December 8, 2024 18:43
@renovate renovate bot changed the title chore(deps): update dependency @vitejs/plugin-vue to v5 - autoclosed chore(deps): update dependency @vitejs/plugin-vue to v5 Dec 9, 2024
@renovate renovate bot reopened this Dec 9, 2024
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 5f3279f to fdee626 Compare December 9, 2024 06:04
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.

0 participants