Support for ESM extensions

[felipecrs]

As I originally reported here:

The vscode-test cli doesn't seem to support testing ESM extensions:

> vscode-test

✔ Validated version: 1.100.0
✔ Found at https://update.code.visualstudio.com/1.100.0/linux-x64/stable?released=true
✔ Downloaded VS Code into /home/felipecrs/repos/vscode-shellcheck/.vscode-test/vscode-linux-x64-1.100.0
[main 2025-05-10T20:13:20.294Z] update#setState disabled
[main 2025-05-10T20:13:20.296Z] update#ctor - updates are disabled by the environment
Started local extension host with pid 87078.
Started initializing default profile extensions in extensions installation folder. file:///home/felipecrs/repos/vscode-shellcheck/.vscode-test/extensions
ComputeTargetPlatform: linux-x64
Completed initializing default profile extensions in extensions installation folder. file:///home/felipecrs/repos/vscode-shellcheck/.vscode-test/extensions
Loading development extension at /home/felipecrs/repos/vscode-shellcheck
Error: Cannot find package 'vscode' imported from /home/felipecrs/repos/vscode-shellcheck/out/src/utils/tool-check.js
        at packageResolve (node:internal/modules/esm/resolve:880:9)
        at moduleResolve (node:internal/modules/esm/resolve:953:18)
        at defaultResolve (node:internal/modules/esm/resolve:1195:11)
        at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12)
        at #cachedDefaultResolve (node:internal/modules/esm/loader:591:25)
        at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:347:53)
        at new ModuleJobSync (node:internal/modules/esm/module_job:333:34)
        at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:407:11)
        at new ModuleJobSync (node:internal/modules/esm/module_job:333:34)
        at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:320:11)
        at loadESMFromCJS (node:internal/modules/cjs/loader:1378:24)
        at Module._compile (node:internal/modules/cjs/loader:1518:5)
        at Module._extensions..js (node:internal/modules/cjs/loader:1588:16)
        at Module.load (node:internal/modules/cjs/loader:1282:32)
        at Module._load (node:internal/modules/cjs/loader:1103:12)
        at c._load (node:electron/js2c/node_init:2:16955)
        at e._load (file:///home/felipecrs/repos/vscode-shellcheck/.vscode-test/vscode-linux-x64-1.100.0/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:225:1509)
        at t._load (file:///home/felipecrs/repos/vscode-shellcheck/.vscode-test/vscode-linux-x64-1.100.0/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:180:22628)
        at r._load (file:///home/felipecrs/repos/vscode-shellcheck/.vscode-test/vscode-linux-x64-1.100.0/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:172:22062)
        at Module.require (node:internal/modules/cjs/loader:1305:19)
        at require (node:internal/modules/helpers:182:18)
        at /home/felipecrs/repos/vscode-shellcheck/node_modules/mocha/lib/mocha.js:416:36
        at Array.forEach (<anonymous>)
        at Mocha.loadFiles (/home/felipecrs/repos/vscode-shellcheck/node_modules/mocha/lib/mocha.js:413:14)
        at Mocha.run (/home/felipecrs/repos/vscode-shellcheck/node_modules/mocha/lib/mocha.js:988:10)
        at mochaGlobalTeardown.mochaGlobalTeardown (/home/felipecrs/repos/vscode-shellcheck/node_modules/@vscode/test-cli/out/runner.cjs:33:50)
        at new Promise (<anonymous>)
        at Object.run (/home/felipecrs/repos/vscode-shellcheck/node_modules/@vscode/test-cli/out/runner.cjs:33:11)
        at file:///home/felipecrs/repos/vscode-shellcheck/.vscode-test/vscode-linux-x64-1.100.0/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:123:17846
        at new Promise (<anonymous>)
        at PJ.sb (file:///home/felipecrs/repos/vscode-shellcheck/.vscode-test/vscode-linux-x64-1.100.0/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:123:17567)
        at async PJ.$extensionTestsExecute (file:///home/felipecrs/repos/vscode-shellcheck/.vscode-test/vscode-linux-x64-1.100.0/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:123:17155)
[main 2025-05-10T20:13:22.099Z] Extension host with pid 87078 exited with code: 0, signal: unknown.
Exit code:   1

[geangontijo]

+1

[daiyam]

I had to move to ESM to be able to use langium...

When using the cli, I get the error:

Started local extension host with pid 94193.
Extension host (LocalProcess pid: 94193) is unresponsive.
UNRESPONSIVE extension host: starting to profile NOW
[main 2025-08-12T12:35:36.386Z] Extension host with pid 94193 exited with code: 0, signal: unknown.
Exit code:   1

With the debugging task, I get the same error as @felipecrs.

[poelstra]

@daiyam Did you ever resolve that issue? I just ran into the exact same problem, running a Langium extension in a vscode-test project.

[daiyam]

No

[mizdra]

The error Cannot find package 'vscode' seems to have been resolved in VS Code 1.101.0. However, there seems to be another issue causing tests to hang.

$ git clone git@github.com:vscode-shellcheck/vscode-shellcheck.git
$ cd vscode-shellcheck
$ git checkout bb3028e
$ npm i
$ npm run build:test
$ VSCODE_TEST_VERSION="1.101.0" npm run test
> shellcheck@0.38.3 test
> vscode-test

✔ Validated version: 1.101.0
✔ Found existing install in /Users/mizdra/src/localhost/gomi/vscode-shellcheck/.vscode-test/vscode-darwin-arm64-1.101.0
[main 2025-12-29T15:58:01.770Z] update#setState disabled
[main 2025-12-29T15:58:01.772Z] update#ctor - updates are disabled by the environment
Via 'product.json#extensionEnabledApiProposals' extension 'ms-vsliveshare.vsliveshare' wants API proposal 'notebookCellExecutionState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.gather' wants API proposal 'notebookCellExecutionState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.vscode-pylance' wants API proposal 'mcpConfigurationProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
Started local extension host with pid 97601.
ChatSessionStore: Migrating 0 chat sessions from storage service to file system
ComputeTargetPlatform: darwin-arm64
Loading development extension at /Users/mizdra/src/localhost/gomi/vscode-shellcheck
Settings Sync: Account status changed from uninitialized to unavailable
Extension host (LocalProcess pid: 97601) is unresponsive.
UNRESPONSIVE extension host: starting to profile NOW
(hang here...)

Upon investigating this issue, it was determined to be a bug in vscode (more precisely, in the Node.js bundled with it). It has been reported at microsoft/vscode#285297.

If you wish to work around this issue, please try the method described in the "Workaround" section of microsoft/vscode#285297.