Fix Vite alias matching for next/* imports

[DavidAlexandre93]

Motivation

• The production build failed because the generic next alias captured subpath imports like next/script, resolving to an incorrect path such as src/shims/next/index.ts/script.
• The goal is to ensure next/* subpath imports resolve to their explicit shims while keeping the base next shim available for exact matches.

Description

• Replaced the object-form resolve.alias with an ordered array of alias entries in vite.config.ts so more specific aliases are matched first.
• Added an exact-match alias { find: /^next$/, replacement: path.resolve(__dirname, "src/shims/next/index.ts") } so next no longer captures next/* imports.
• Kept explicit aliases for next/* and next-i18next/* shims to preserve existing behavior for those subpaths.

Testing

• Ran npm run build, which could not complete in this environment because vite is not installed locally and the command failed.
• Ran npm install to restore dependencies, which failed due to 403 Forbidden from the npm registry, preventing a full validation of the production build.

---

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.