Bump vite from 6.4.1 to 6.4.2 in /dotnet/samples/Demos/ProcessWithCloudEvents/ProcessWithCloudEvents.Client

[dependabot]

Bumps vite from 6.4.1 to 6.4.2.

Release notes

Sourced from vite's releases.

v6.4.2

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

6.4.2 (2026-04-06)

• fix: apply server.fs check to env transport (#22159) (#22163) (fe28e47), closes #22159 #22163
• fix: avoid path traversal with optimize deps sourcemap handler (#22161) (ca4da5d), closes #22161

Commits

• 6b3fad0 release: v6.4.2
• ca4da5d fix: avoid path traversal with optimize deps sourcemap handler (#22161)
• fe28e47 fix: apply server.fs check to env transport (#22159) (#22163)
• 5487f4f release: v6.4.1
• 1114b5d fix(dev): trim trailing slash before server.fs.deny check (#20968) (#20969)
• f12697c release: v6.4.0
• ca6455e feat: allow passing down resolved config to vite's createServer (#20932)
• 0e173d8 release: v6.3.7
• c59a222 fix(esbuild): inject esbuild helpers correctly for esbuild 0.25.9+ (#20940)
• 3f337c5 release: v6.3.6
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

Automated Code Review

Reviewers: 4 | Confidence: 91%

✓ Correctness

This is a straightforward patch-level dependency bump of vite from 6.4.1 to 6.4.2 in a demo client project. The changes span package.json, package-lock.json, and yarn.lock, all consistently reflecting the version update. The removal of "peer": true flags on numerous transitive dependencies in package-lock.json indicates these packages were previously only pulled in as peer dependencies but are now resolved as direct/transitive dependencies — this is a normal lockfile regeneration artifact and not a correctness concern. No logic, configuration, or source code changes are involved.

✓ Security Reliability

This PR is a straightforward patch version bump of the vite dev dependency from ^6.4.1 to ^6.4.2 in a sample client project, along with corresponding lockfile updates. The removal of 'peer' flags in package-lock.json is consistent with a lockfile regeneration. No security or reliability concerns are introduced by this change.

✓ Test Coverage

This PR is a straightforward dependency version bump of vite from ^6.4.1 to ^6.4.2 in a dotnet sample demo's React client app (ProcessWithCloudEvents.Client). The changes are limited to package.json, package-lock.json, and yarn.lock. As a minor patch version bump of a dev dependency in a sample/demo project, no new behavior is introduced and no test coverage changes are needed. The removal of 'peer' flags in package-lock.json entries is a normal side effect of the lockfile regeneration and does not affect runtime behavior.

✓ Design Approach

This PR bumps vite from 6.4.1 to 6.4.2 in a sample project and regenerates both lock files. The vite update itself is straightforward and appropriate. However, the repository maintains both package-lock.json (npm) and yarn.lock (yarn) simultaneously. This is a design problem: two competing lock files create ambiguity about which package manager is authoritative, can easily drift out of sync (as seen here where npm and yarn resolve the registry URL differently), and forces contributors to maintain both. The project should commit to a single package manager and delete the other lock file. The mass removal of 'peer: true' annotations throughout package-lock.json is simply an artifact of npm regenerating the lockfile under a different npm version and is not itself a concern.

Suggestions

• The project maintains both package-lock.json (npm) and yarn.lock (yarn) simultaneously. Pick one package manager and remove the other lock file to avoid ambiguity and silent drift — e.g., the yarn.lock resolves vite from registry.yarnpkg.com while package-lock.json uses registry.npmjs.org, and there is no guarantee both will always agree on resolved versions.

---

Automated review by dependabot[bot]'s agents