Npm fails after 'Rebuild Container'

[egamma]

1. Clone https://github.com/microsoft/vscode-remote-try-node into a container volume
2. npm install works fine
3. Run Rebuild Container
4. npm install get the following error:

node@1493723f89c2:/workspaces/vscode-remote-try-node$ npm install
internal/modules/cjs/loader.js:968
  throw err;
  ^

Error: Cannot find module '/home/node/.vscode-server-insiders/data/User/workspaceStorage/fbaf90b076ac78e0d27774a5306a7fcd/ms-vscode.js-debug/bootloader.js'
Require stack:
- internal/preload
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:965:15)
    at Function.Module._load (internal/modules/cjs/loader.js:841:27)
    at Module.require (internal/modules/cjs/loader.js:1025:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:1277:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:439:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:71:3)
    at internal/main/run_main_module.js:7:1 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 'internal/preload' ]
}

Running node or npm fails with the same exception.

[chrmarti]

Related: microsoft/vscode-js-debug#374 (comment)

[egamma]

After following the steps given in the comment both npm and node work again.

[chrmarti]

@connor4312 Is this still the old issue or is this a new case?

[connor4312]

This is interesting. @Tyriar we should discard the terminal environment variables when rebuilding a container, treat it as a new workspace.

[chrmarti]

@connor4312 A rebuild also reloads the window, are the variables preserved across reloads?

[connor4312]

Yes, intentionally

[Tyriar]

@chrmarti are there any hooks that I can use to clear the environment variable collections? It is just a regular window reload from the perspective of VS Code?

[chrmarti]

@Tyriar The reload is not aware of the rebuild, only the extension nows about that. There are no hooks I'm aware of. What is the environment variable that causes this?