feat(optimizer): improve dependency optimization error messages with esbuild formatMessages

[Copilot]

Closes #13361

When esbuild fails during dependency optimization, users receive cryptic error messages without context about where the error occurred. This makes it difficult to understand that the issue is related to dependency optimization settings rather than the main build process.

Problem

Users would see confusing errors like:

Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)

Without any indication that this error happened during dependency optimization, users struggle to understand:

• That the error is related to optimizeDeps.esbuildOptions.target settings
• How to fix it by adjusting the target or excluding problematic dependencies
• That this is separate from their main build target configuration

Solution

Enhanced error handling using esbuild's formatMessages API to provide properly formatted error messages with context. The implementation follows the established pattern from the dependency scanner.

After this change

Users will now see:

Error during dependency optimization:

Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)

This immediately signals that:

1. The error is happening during dependency optimization
2. They should look at optimizeDeps configuration options
3. They can potentially fix it by setting optimizeDeps.esbuildOptions.target to a higher target like 'esnext'

Implementation

The implementation uses esbuild's formatMessages API to properly format error messages with colors while preserving the original error object and stack trace. This approach:

• Maintains consistency with the existing error handling pattern in the dependency scanner
• Provides better formatted error output for esbuild errors
• Preserves all original error information including stack traces
• Uses consistent color formatting throughout the codebase

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[sapphi-red]

/ecosystem-ci run

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/vite@20525

commit: 4d6a070

[vite-ecosystem-ci]

📝 Ran ecosystem CI on 4d6a070: Open

suite	result	latest scheduled
histoire	❌ failure	✅ success
vike	✅ success	❌ failure
vitest	❌ failure	❌ failure
waku	❌ failure	✅ success

✅ laravel, nuxt, analogjs, marko, qwik, quasar, one, ladle, react-router, astro, storybook, vite-plugin-pwa, vite-environment-examples, rakkas, sveltekit, vite-plugin-svelte, vite-plugin-vue, vuepress, unocss, vitepress, vite-plugin-cloudflare, vite-setup-catalogue, vite-plugin-rsc, vite-plugin-react