@@ -3,7 +3,6 @@ import * as cp from 'child_process';
3
3
import { VSBuffer } from 'vs/base/common/buffer' ;
4
4
import { Emitter } from 'vs/base/common/event' ;
5
5
import { FileAccess } from 'vs/base/common/network' ;
6
- import { join } from 'vs/base/common/path' ;
7
6
import { INativeEnvironmentService } from 'vs/platform/environment/common/environment' ;
8
7
import { IRemoteExtensionHostStartParams } from 'vs/platform/remote/common/remoteAgentConnection' ;
9
8
import { getNlsConfiguration } from 'vs/server/nls' ;
@@ -168,10 +167,17 @@ export class ExtensionHostConnection extends Connection {
168
167
this . logger . debug ( 'Spawning extension host...' ) ;
169
168
const proc = cp . fork (
170
169
FileAccess . asFileUri ( 'bootstrap-fork' , require ) . fsPath ,
171
- // While not technically necessary, makes it easier to tell which process
172
- // bootstrap-fork is executing. Can also do pkill -f extensionHost
173
- // Other spawns in the VS Code codebase behave similarly.
174
- [ '--type=extensionHost' , `--uriTransformerPath=${ join ( FileAccess . asFileUri ( 'bootstrap-fork' , require ) . fsPath , '../../../../out/node/uri_transformer.js' ) } ` ] ,
170
+ [
171
+ // While not technically necessary, adding --type makes it easier to
172
+ // tell which process bootstrap-fork is executing. Can also do `pkill -f
173
+ // extensionHost`. Other spawns in the VS Code codebase behave
174
+ // similarly.
175
+ '--type=extensionHost' ,
176
+ // We can't use the symlinked uriTransformer in this same directory
177
+ // because it gets compiled into AMD syntax and this path is imported
178
+ // using Node's native require.
179
+ `--uriTransformerPath=${ FileAccess . asFileUri ( 'vs/../../../../out/node/uriTransformer.js' , require ) . fsPath } `
180
+ ] ,
175
181
{
176
182
env : {
177
183
...process . env ,
0 commit comments