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 #242

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 1, 2024

This PR contains the following updates:

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

Release Notes

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

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


Configuration

📅 Schedule: Branch creation - "before 5am on the first day of the month" (UTC), 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 Mar 1, 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vite
npm ERR!   dev vite@"4.3.9" 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-03-01T04_27_51_960Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 7b7093b to 4d6c902 Compare May 31, 2024 09:10
Copy link
Contributor Author

renovate bot commented May 31, 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vite
npm ERR!   dev vite@"4.3.9" 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.1.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-09-18T02_25_49_677Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch 2 times, most recently from 9579558 to 6f3d77c Compare July 27, 2024 09:41
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 6f3d77c to 53ee1a3 Compare August 1, 2024 16:49
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 53ee1a3 to 313dafe Compare August 29, 2024 18:51
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 313dafe to 64bcee5 Compare September 18, 2024 02:25
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