Update dependency laravel-vite-plugin to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
laravel-vite-plugin	0.8.1 → 3.0.0

---

Release Notes

laravel/vite-plugin (laravel-vite-plugin)

v3.0.0

Compare Source

What's Changed

• [3.x] Add Vite 8 support by @​timacdonald in #​342

Please see the upgrade guide for important upgrade steps.

Full Changelog: laravel/vite-plugin@v2.1.0...v3.0.0

v2.1.0

Compare Source

• fix: missing 2.0.0 release notes in changelog by @​james2doyle in #​338
• [2.x] Use vite export to future proof additional pattern changes by @​timacdonald in #​339

v2.0.1

Compare Source

• Automatically create hotFile parent directory by @​adrum in #​334

v2.0.0

Compare Source

• Vite 7 Support by @​sweptsquash in #​328
• Upgrade dependencies by @​timacdonald in #​331

v1.3.0

Compare Source

• Use rollup types from Vite by @​sapphi-red in #​325

v1.2.0

Compare Source

• [1.x] Fix Invalid URL issue with Vite 6.0.9 by @​batinmustu in #​317
• [1.x] Add default CORS origins by @​timacdonald in #​318

v1.1.1

Compare Source

• [1.1] Fix dependency issue with Vite 5 by @​jessarcher in #​313

v1.1.0

Compare Source

• Upgrade to Vite 6 by @​timacdonald in #​310

v1.0.6

Compare Source

• Replace dead link in Security Policy by @​Jubeki in #​300
• Look for certificates in valet linux config directory by @​jameshulse in #​307

v1.0.5

Compare Source

• TypeScript: define entrypoints using object by @​tylerlwsmith in #​298

v1.0.4

Compare Source

• Include base in hotFile without modifying server.origin replacement by @​danielztolnai in #​296

v1.0.3

Compare Source

• Append base to hot file by @​timacdonald in #​290
• Support Laravel Herd for windows by @​mozex in #​293

v1.0.2

Compare Source

• [1.x] Fix HMR issue when resources/lang directory doesn't exist and a symlink is present in the root directory by @​jessarcher in #​285

v1.0.1

Compare Source

• [1.x] Simpler conditional by @​Jubeki in #​273
• [1.x] Account for imported CSS files while cleaning by @​timacdonald in #​275
• [1.x] Fix exit error messages by @​timacdonald in #​276

v1.0.0

Compare Source

• [1.0] Drop CJS build and export types first by @​benmccann in #​235
• [1.x] Introduce clean-orphaned-assets binary by @​timacdonald in #​251
• [0.8.x] Respect vite server.origin in viteDevServerUrl by @​nurdism in #​255
• [1.x] Vite 5 by @​timacdonald in #​269
• [0.8.x] Fallback pages by @​timacdonald in #​271
• [1.x] Auto detect Valet / Herd TLS certificates by @​timacdonald in #​180

---

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 is behind base branch, 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]

⚠️ 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: undefined@undefined
npm ERR! Found: vite@3.2.11
npm ERR! node_modules/vite
npm ERR!   dev vite@"3.2.11" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^8.0.0" from laravel-vite-plugin@3.0.0
npm ERR! node_modules/laravel-vite-plugin
npm ERR!   dev laravel-vite-plugin@"3.0.0" 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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-03-19T05_55_04_375Z-debug-0.log