chore(deps-dev): bump vite from 7.3.1 to 8.0.0#1
chore(deps-dev): bump vite from 7.3.1 to 8.0.0#1dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 7.3.1 to 8.0.0. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/[email protected]/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 8.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
📝 WalkthroughWalkthroughThe vite dev dependency has been upgraded from version 7.3.1 to 8.0.0 in package.json. This represents a major version bump for the build tool. Changes
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 14: The package.json currently declares "vite": "^8.0.0" while
"laravel-vite-plugin@^2.1.0" requires a peer of "vite: ^7.0.0"; resolve the
peer-dependency mismatch by either upgrading the laravel-vite-plugin to a
version that supports Vite 8 (find and bump "laravel-vite-plugin" to the
compatible release) or by downgrading "vite" back to a 7.x range (change the
"vite" entry to a 7.x semver); after making the change, run npm/yarn install and
verify the lockfile updates and a successful local build to confirm the conflict
is resolved.
| "postcss": "^8.4.47", | ||
| "tailwindcss": "^4.1.18", | ||
| "vite": "^7.3.1" | ||
| "vite": "^8.0.0" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "1) Confirm declared versions"
jq -r '.devDependencies | {vite, "laravel-vite-plugin": ."laravel-vite-plugin"}' package.json
echo
echo "2) Locate HMR accept usages that may need manual review under Vite 8"
rg -nP -C2 'import\.meta\.hot\.accept\s*\('
echo
echo "3) Locate explicit build target settings that may rely on old defaults"
rg -nP -C2 '\btarget\b'Repository: dAppCore/php-admin
Length of output: 218
🌐 Web query:
laravel-vite-plugin 2.1.0 Vite 8.0.0 compatibility
💡 Result:
[email protected] is not officially compatible with Vite 8.0.0.
- Its
peerDependenciesrequirevite: ^7.0.0(so[email protected]is outside the supported range and will trigger a peer-dependency conflict in npm/pnpm). [1] - If you want Vite 8, you’ll need to wait for a laravel-vite-plugin release that widens the peer dependency to include Vite 8, or stay on Vite 7 for a supported setup. (You can force-install despite peer deps, but it’s unsupported and may break.) [1][2]
Sources:
[1] laravel/vite-plugin v2.1.0 package.json (peerDependencies) (raw.githubusercontent.com)
[2] Vite 8 beta announcement / migration guidance (vite.dev)
Citations:
- 1: https://raw.githubusercontent.com/laravel/vite-plugin/v2.1.0/package.json
- 2: https://vite.dev/blog/announcing-vite8-beta?utm_source=openai
Update laravel-vite-plugin or downgrade Vite before merging.
The declared laravel-vite-plugin@^2.1.0 has a peer dependency requirement of vite: ^7.0.0. Upgrading Vite to 8.0.0 creates a peer-dependency conflict and an unsupported configuration that may cause build or runtime failures. Either upgrade laravel-vite-plugin to a version that supports Vite 8, or revert Vite to version 7.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 14, The package.json currently declares "vite":
"^8.0.0" while "laravel-vite-plugin@^2.1.0" requires a peer of "vite: ^7.0.0";
resolve the peer-dependency mismatch by either upgrading the laravel-vite-plugin
to a version that supports Vite 8 (find and bump "laravel-vite-plugin" to the
compatible release) or by downgrading "vite" back to a 7.x range (change the
"vite" entry to a 7.x semver); after making the change, run npm/yarn install and
verify the lockfile updates and a successful local build to confirm the conflict
is resolved.
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps vite from 7.3.1 to 8.0.0.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
ea68a88chore(deps): update rolldown-related dependencies (#20810)693d255release: v7.1.798a3484fix(hmr): wait forimport.meta.hot.prunecallbacks to complete before runni...9f32b1dfix(hmr): trigger prune event when import is removed from non hmr module (#20...9f2247cfix(deps): update all non-major dependencies (#20811)105abe8fix(glob): handle glob imports from folders starting with dot (#20800)4c4583cfix(build): fix ssr environmentemitAssets: truewhen `sharedConfigBuild: t...9bc9d12fix(client): use CSP nonce when rendering error overlay (#20791)54377f7release: v7.1.688af2aefix(deps): update all non-major dependencies (#20773)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by CodeRabbit