fix: cannot open vscode when use vscode-win32-x64 in Windows

[BlackHole1]

When executing npm run gulp vscode-win32-x64 on the Windows platform, the bundle-vscode task is triggered. However, this task does not handle the path issues well, resulting in the contents of the bootstrap-window.js file not being injected into workbench.js and processExplorer.js.

The reason why VSCode does not encounter this issue is that the code compilation (compile-build) is performed on a Linux machine, while the Windows machine only executes the application build (vscode-win32-x64-ci will not trigger bundle-vscode).

PTAL @deepak1556

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.

Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more

[bpasero]

There also seems to be another case here:

vscode/build/gulpfile.vscode.web.js

Lines 93 to 112 in 4ad5865

	return path => {
	if (path.endsWith('vs/platform/product/common/product.js')) {
	return content => {
	const productConfiguration = JSON.stringify({
	...product,
	version,
	commit,
	date: readISODate('out-build')
	});
	return content.replace('/*BUILD->INSERT_PRODUCT_CONFIGURATION*/', () => productConfiguration.substr(1, productConfiguration.length - 2) /* without { and }*/);
	};
	} else if (path.endsWith('vs/workbench/services/extensionManagement/browser/builtinExtensionsScannerService.js')) {
	return content => {
	const builtinExtensions = JSON.stringify(extensions.scanBuiltinExtensions(extensionsRoot));
	return content.replace('/*BUILD->INSERT_BUILTIN_EXTENSIONS*/', () => builtinExtensions.substr(1, builtinExtensions.length - 2) /* without [ and ]*/);
	};
	}
	return undefined;
	};

[BlackHole1]

@bpasero Done

[bpasero]

Thanks, we are actually checking in the related JS file as well, so can you run a npm run compile in the build folder and check that in?

[BlackHole1]

@bpasero Completed.