Different vallues module.expots and exports

[LutAle]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version:
• OS Version:

Версия: 1.67.0 (system setup)
Фиксация: 57fd6d0
Дата: 2022-05-04T12:06:02.889Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
ОС: Windows_NT x64 10.0.19044

I debug code extension JS code

const vscode = require('vscode');
// ..
function activate() {}
function deactivate() {}
// case 1
exports = {activate , deactivate}  // not works not call activate function 
// case 0 
// module.exports = {activate , deactivate}  //  ok - works 

Steps to Reproduce:

After evaluate exports assigment internal state chnge to wrong values. module.exports not same as exports

[roblourens]

Please explain some more about what you are trying to do

[LutAle]

I think that module.exports and exports thatx reference for same object

[LutAle]

exports === module.exports === single, in memory object {} for all time runtime

[roblourens]

Do you know anything about this @jrieken? Do we manipulate these when loading extensions?

[jrieken]

@LutAle Is the extension running in the nodejs extension host or web worker extension host?

[LutAle]

@jrieken In node extension host. A get explain this assertion, - for node export.module object put other object in module.export and exports not reference new module.exports object

[vscodenpa]

Hey @roblourens, this issue might need further attention.

@LutAle, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!