chore(deps): replace dependency vite with vite 8.0.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
vite (source)	pnpm-workspace.overrides	replacement	7.3.1 → 8.0.0
vite (source)	devDependencies	replacement	7.3.1 → 8.0.0

---

Warning

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

This is a special PR that replaces vite with the community suggested minimal stable replacement version.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
• 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 these updates 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: pnpm-lock.yaml

Scope: all 22 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 39, reused 0, downloaded 0, added 0
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for vite@npm:rolldown-vite@8.0.0 while fetching it from https://registry.npmjs.org/

This error happened while installing a direct dependency of /tmp/renovate/repos/github/launchdarkly/launchpad-ui

The latest release of rolldown-vite is "7.3.1".

Other releases are:
  * alpha: 7.0.0-alpha.0
  * beta: 7.2.0-beta.3

If you need the full list of all 92 published versions run "pnpm view rolldown-vite versions".
Progress: resolved 56, reused 0, downloaded 0, added 0

[changeset-bot]

⚠️ No Changeset found

Latest commit: ae3582d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ae3582d. Configure here.}

[cursor]

Invalid Vite 8 replacement alias

High Severity

The bump replaces vite with npm:rolldown-vite@8.0.0, but rolldown-vite stopped at 7.3.1 and was archived when Rolldown landed in core Vite 8. That version is not published, so installs fail. Vite’s migration path drops the alias and depends on vite@8 directly.

Additional Locations (1)

• pnpm-workspace.yaml#L18-L19

 

^{Reviewed by Cursor Bugbot for commit ae3582d. Configure here.}

[cursor]

Stale Vite peer allowlist

Medium Severity

The Vite override moves to version 8, but peerDependencyRules.allowedVersions.vite still only allows 6 || 7 while strictPeerDependencies is enabled. Several tooling peers (including @vitejs/plugin-react-oxc and @vitejs/plugin-react-swc) do not declare Vite 8, so installs can fail on peer mismatches.

Additional Locations (1)

• pnpm-workspace.yaml#L18-L19

 

^{Reviewed by Cursor Bugbot for commit ae3582d. Configure here.}