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

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

Update dependency @vitejs/plugin-vue to v5 #284

wants to merge 1 commit into from
+2 −2

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 12, 2024 •
edited
Loading

This PR contains the following updates:

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

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

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

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

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.

@renovate renovate bot requested a review from acekyd as a code owner October 12, 2024 01:41
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Oct 12, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Oct 12, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update artifacts 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: javascript/todo/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"4.5.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^5.0.0" from @vitejs/[email protected]
npm error node_modules/@vitejs/plugin-vue
npm error   dev @vitejs/plugin-vue@"5.2.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-11-13T11_39_18_403Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-13T11_39_18_403Z-debug-0.log
File name: javascript/todo-starter/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"4.5.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^5.0.0" from @vitejs/[email protected]
npm error node_modules/@vitejs/plugin-vue
npm error   dev @vitejs/plugin-vue@"5.2.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-11-13T11_39_24_267Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-13T11_39_24_267Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch 3 times, most recently from aae311b to 963806c Compare October 18, 2024 19:40
@finn-block
Copy link
Member

Blocked on haoqunjiang/vite-plugin-node-stdlib-browser#9

@finn-block finn-block added the blocked this PR or issue can't advance due to some external issue label Oct 29, 2024
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 963806c to 54068ff Compare November 11, 2024 04:14
@renovate renovate bot force-pushed the renovate/vitejs-plugin-vue-5.x branch from 54068ff to a0c9f73 Compare November 13, 2024 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@acekyd acekyd Awaiting requested review from acekyd acekyd is a code owner

@blackgirlbytes blackgirlbytes Awaiting requested review from blackgirlbytes blackgirlbytes is a code owner

Assignees
No one assigned
Labels
blocked this PR or issue can't advance due to some external issue dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@finn-block