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

Update dependency vite to v5 #35

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 19, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) ^4.4.2 -> ^5.0.0 age adoption passing confidence

Release Notes

vitejs/vite (vite)

v5.4.8

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.7

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.6

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.5

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.4

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.3

Compare Source

Copy link
Contributor Author

renovate bot commented Nov 19, 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @sveltejs/[email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"^5.0.0" from the root project
npm error   peer vite@">=3" from [email protected]
npm error   node_modules/vite-plugin-mkcert
npm error     dev vite-plugin-mkcert@"^1.11.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^4.0.0" from @sveltejs/[email protected]
npm error node_modules/@sveltejs/kit
npm error   dev @sveltejs/kit@"^1.20.4" from the root project
npm error   peer @sveltejs/kit@"^1.0.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/adapter-auto
npm error     dev @sveltejs/adapter-auto@"^2.0.0" from the root project
npm error   1 more (@sveltejs/adapter-cloudflare)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/vite
npm error   peer vite@"^4.0.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/kit
npm error     dev @sveltejs/kit@"^1.20.4" from the root project
npm error     peer @sveltejs/kit@"^1.0.0" from @sveltejs/[email protected]
npm error     node_modules/@sveltejs/adapter-auto
npm error       dev @sveltejs/adapter-auto@"^2.0.0" from the root project
npm error     1 more (@sveltejs/adapter-cloudflare)
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-04-26T03_16_18_694Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/vite-5.x branch 7 times, most recently from d511847 to dd2f1b1 Compare November 24, 2023 13:15
@renovate renovate bot force-pushed the renovate/vite-5.x branch 6 times, most recently from 11347b3 to 6c92aa3 Compare December 8, 2023 22:50
@renovate renovate bot force-pushed the renovate/vite-5.x branch 5 times, most recently from b29e7f2 to bcf8e12 Compare December 19, 2023 04:36
@renovate renovate bot force-pushed the renovate/vite-5.x branch 3 times, most recently from 7e3c7b0 to 7590ac7 Compare January 22, 2024 20:03
@renovate renovate bot force-pushed the renovate/vite-5.x branch 2 times, most recently from 564f720 to ba8996d Compare February 20, 2024 01:50
@renovate renovate bot force-pushed the renovate/vite-5.x branch 3 times, most recently from af82aa2 to 943471e Compare March 1, 2024 04:17
@renovate renovate bot force-pushed the renovate/vite-5.x branch 3 times, most recently from f496f58 to ce49aa6 Compare March 27, 2024 17:07
@renovate renovate bot force-pushed the renovate/vite-5.x branch 4 times, most recently from e149585 to f159042 Compare April 16, 2024 02:05
@renovate renovate bot force-pushed the renovate/vite-5.x branch 2 times, most recently from ebe62c3 to c3fb4d7 Compare April 26, 2024 03:16
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 could not resolve
npm error
npm error While resolving: @sveltejs/[email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"^5.0.0" from the root project
npm error   peer vite@">=3" from [email protected]
npm error   node_modules/vite-plugin-mkcert
npm error     dev vite-plugin-mkcert@"^1.11.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^4.0.0" from @sveltejs/[email protected]
npm error node_modules/@sveltejs/kit
npm error   dev @sveltejs/kit@"^1.20.4" from the root project
npm error   peer @sveltejs/kit@"^1.0.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/adapter-auto
npm error     dev @sveltejs/adapter-auto@"^2.0.0" from the root project
npm error   1 more (@sveltejs/adapter-cloudflare)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/vite
npm error   peer vite@"^4.0.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/kit
npm error     dev @sveltejs/kit@"^1.20.4" from the root project
npm error     peer @sveltejs/kit@"^1.0.0" from @sveltejs/[email protected]
npm error     node_modules/@sveltejs/adapter-auto
npm error       dev @sveltejs/adapter-auto@"^2.0.0" from the root project
npm error     1 more (@sveltejs/adapter-cloudflare)
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-09-30T07_14_25_509Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-30T07_14_25_509Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vite-5.x branch 2 times, most recently from d165e44 to 2b72e52 Compare May 17, 2024 07:30
@renovate renovate bot force-pushed the renovate/vite-5.x branch 3 times, most recently from 4a2f3a2 to 4a62ede Compare June 13, 2024 10:08
@renovate renovate bot force-pushed the renovate/vite-5.x branch 2 times, most recently from befcc23 to 9139a39 Compare June 20, 2024 19:32
@renovate renovate bot force-pushed the renovate/vite-5.x branch 2 times, most recently from 3409b50 to 9c36a16 Compare July 29, 2024 00:39
@renovate renovate bot force-pushed the renovate/vite-5.x branch 3 times, most recently from e3a10d5 to ff6d668 Compare September 20, 2024 02:19
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