Isolate content script build to prevent silent chunk-import breakage

package.json

@@ -5,7 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "vite build --watch --mode development",
-    "build": "tsc && vite build",
+    "build": "tsc && vite build && vite build --config vite.content.config.ts",
     "preview": "vite preview",
     "type-check": "tsc --noEmit",
     "generate-manifest": "node scripts/generate-manifest.js"

vite.config.ts

@@ -41,8 +41,7 @@ export default defineConfig({
         options: resolve(__dirname, 'src/options/options.html'),
         background: resolve(__dirname, 'src/background/service-worker.ts'),
         offscreen: resolve(__dirname, 'src/offscreen/offscreen.ts'),
-        share: resolve(__dirname, 'src/share/share.tsx'),
-        'content/selection-overlay': resolve(__dirname, 'src/content/selection-overlay.ts')
+        share: resolve(__dirname, 'src/share/share.tsx')
       },
       output: {
         entryFileNames: '[name].js',

vite.content.config.ts

@@ -0,0 +1,32 @@
+import { defineConfig } from 'vite';
+import { resolve } from 'path';
+
+/**
+ * Separate Vite config for content scripts.
+ *
+ * Content scripts injected via chrome.scripting.executeScript must be
+ * completely self-contained — they cannot resolve ES module chunk imports
+ * at runtime. Building content scripts as a single-entry point ensures that
+ * all static imports are bundled inline and no shared chunks are emitted.
+ */
+export default defineConfig({
+  base: './',
+  resolve: {
+    alias: {
+      '@': resolve(__dirname, './src')
+    }
+  },
+  build: {
+    outDir: 'dist',
+    emptyOutDir: false,
+    rollupOptions: {
+      input: {
+        'content/selection-overlay': resolve(__dirname, 'src/content/selection-overlay.ts')
+      },
+      output: {
+        entryFileNames: '[name].js',
+        assetFileNames: '[name].[ext]'
+      }
+    }
+  }
+});