fix(e2e): use vite dev server for realistic Spotlight testing

Switch from vite build+preview to vite dev server because:
- Spotlight is designed for development mode
- Dev server automatically uses 'development' exports from SDK
- More realistic test of how users would use Spotlight

Changes:
- test:build now only runs install (no build needed for dev server)
- playwright starts 'pnpm dev' instead of 'pnpm preview'
- Removed resolve.conditions hack (dev server handles this)

Author: BYK

dev-packages/e2e-tests/test-applications/browser-webworker-vite/package.json

@@ -4,11 +4,11 @@
   "version": "0.0.0",
   "type": "module",
   "scripts": {
-    "dev": "vite",
+    "dev": "vite --port 3030",
     "build": "rm -rf dist && tsc && vite build",
     "preview": "vite preview --port 3030",
     "test": "playwright test",
-    "test:build": "pnpm install && pnpm build",
+    "test:build": "pnpm install",
     "test:assert": "pnpm test"
   },
   "devDependencies": {

dev-packages/e2e-tests/test-applications/browser-webworker-vite/playwright.config.mjs

@@ -1,7 +1,8 @@
 import { getPlaywrightConfig } from '@sentry-internal/test-utils';
 
 const config = getPlaywrightConfig({
-  startCommand: `pnpm preview`,
+  // Use vite dev server to test development-mode behavior (e.g., Spotlight auto-enablement)
+  startCommand: `pnpm dev`,
   eventProxyFile: 'start-event-proxy.mjs',
   eventProxyPort: 3031,
   port: 3030,

dev-packages/e2e-tests/test-applications/browser-webworker-vite/vite.config.ts

@@ -13,12 +13,6 @@ export default defineConfig({
     },
   },
 
-  // Use development exports from @sentry/* packages to include Spotlight auto-enablement code
-  // The SDK has conditional exports: "development" includes Spotlight, "production" strips it
-  resolve: {
-    conditions: ['development', 'module', 'browser', 'import'],
-  },
-
   plugins: [
     sentryVitePlugin({
       org: process.env.E2E_TEST_SENTRY_ORG_SLUG,