chore: mitigate esbuild audit vulnerability by upgrading vite and overriding esbuild

[DavidAlexandre93]

Motivation

• Resolve npm audit finding where vulnerable esbuild (<=0.24.2) could be pulled transitively via older vite versions.
• Apply a minimally invasive policy change to prevent installation of vulnerable esbuild without performing a full install in an environment that blocks registry operations.

Description

• Updated devDependencies.vite in package.json from ^5.4.11 to ^6.1.7 to move away from vite ranges that depend on vulnerable esbuild versions.
• Added an overrides entry in package.json forcing esbuild to ^0.25.0 so transitive resolution cannot select <=0.24.2.
• No changes to package-lock.json were made because the environment prevents npm install/lockfile updates due to registry 403 errors.

Testing

• Verified the updated fields with npm pkg get devDependencies.vite overrides.esbuild, which returned the new vite and overrides entries successfully.
• Attempted npm audit --json to validate the audit result but the run failed with a 403 Forbidden response from the npm advisories endpoint, so automated audit confirmation could not be completed in this environment.
• Attempted npm install -D vite@^6.1.7 but the install failed due to 403 Forbidden responses from the registry, preventing lockfile and local dependency resolution updates.

---

Codex Task

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 8 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/david-alexandre-fernandes-projects?upgradeToPro=build-rate-limit

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.