Fix: Also handle require() calls when fixing deep relative imports

Add support for require() patterns in addition to import statements.
When tsup/esbuild processes external imports, they might be transformed
to require() calls, so we need to fix those paths too.

Author: Tajudeen

src/vs/workbench/contrib/cortexide/browser/react/build.js

@@ -243,6 +243,7 @@ if (isWatch) {
 			// This fixes imports like: import { x } from '../../../../../base/common/platform.js'
 			// which come from files like systemInfo.ts that import VS Code internal modules
 			// Match any relative import (../...) that leads to base/platform/editor/workbench and add one more level
+			// Handle: import statements, dynamic imports, and require() calls
 			content = content.replace(
 				/(from\s+['\"])((?:\.\.\/)+)(base|platform|editor|workbench)\//g,
 				(match, prefix, dots, module) => `${prefix}${dots}../${module}/`
@@ -251,6 +252,10 @@ if (isWatch) {
 				/(import\s*\(\s*['\"])((?:\.\.\/)+)(base|platform|editor|workbench)\//g,
 				(match, prefix, dots, module) => `${prefix}${dots}../${module}/`
 			);
+			content = content.replace(
+				/(require\(['\"])((?:\.\.\/)+)(base|platform|editor|workbench)\//g,
+				(match, prefix, dots, module) => `${prefix}${dots}../${module}/`
+			);
 
 			fs.writeFileSync(indexPath, content, 'utf8');
 		}