fix: mark React output imports as external during DTS generation to prevent build errors

Author: Tajudeen

src/vs/workbench/contrib/cortexide/browser/react/tsup.config.js

@@ -27,6 +27,19 @@ const externalVSCodePlugin = {
 	}
 }
 
+// Plugin to mark React output imports as external during DTS generation
+// This prevents tsup from trying to resolve imports to files that don't exist yet during the build
+const externalReactOutputsPlugin = {
+	name: 'external-react-outputs',
+	setup(build) {
+		build.onResolve({ filter: /^\.\/react\/out\/|^\.\.\/react\/out\// }, (args) => {
+			// Mark React output imports as external during build (they'll be available at runtime)
+			// This prevents DTS generation from failing when these files don't exist yet
+			return { path: args.path, external: true }
+		})
+	}
+}
+
 export default defineConfig({
 	entry: [
 		'./src2/void-editor-widgets-tsx/index.tsx',
@@ -51,8 +64,7 @@ export default defineConfig({
 	outExtension: () => ({ js: '.js' }),
 	treeshake: true,
 	// Mark Node.js built-ins as external
-	// Note: React output files are NOT marked as external here because they need to be
-	// bundled together. The external plugin handles VS Code imports only.
+	// React output imports are handled by the externalReactOutputsPlugin to prevent DTS generation errors
 	external: [
 		'url', 'module', 'fs', 'path', 'os', 'crypto', 'stream', 'util', 'events', 'buffer', 'process',
 	],
@@ -63,8 +75,9 @@ export default defineConfig({
 		// Note: Memory limits are set via Node.js --max-old-space-size flag in build.js
 		// Use tsconfig.json which already has experimentalDecorators enabled
 		options.tsconfig = './tsconfig.json'
-		// Add plugin to mark VS Code code as external
+		// Add plugins to mark VS Code code and React outputs as external
 		options.plugins = options.plugins || []
 		options.plugins.push(externalVSCodePlugin)
+		options.plugins.push(externalReactOutputsPlugin)
 	}
 })