Debugging Error in Version 1.59.0 Preventing Task Progress

[sowjanyagunupuru]

Hiii,

I am currently facing an issue while debugging in version 1.59.0, where I'm encountering an error. To resolve this, I tried deleting the node_modules folder and the yarn.lock file, followed by reinstalling the dependencies. Despite these efforts, the issue persists.

Error: Cannot find module 'D:\App\sampleIde\\node_modules\@modelcontextprotocol\sdk\dist\client\stdio'
    at createEsmNotFoundErr (node:internal/modules/cjs/loader:1262:15)
    at finalizeEsmResolution (node:internal/modules/cjs/loader:1250:15)
    at resolveExports (node:internal/modules/cjs/loader:634:14)
    at Module._findPath (node:internal/modules/cjs/loader:724:31)
    at Module._resolveFilename (node:internal/modules/cjs/loader:1211:27)
    at Module._load (node:internal/modules/cjs/loader:1051:27)
    at Module.require (node:internal/modules/cjs/loader:1311:19)
    at require (node:internal/modules/helpers:179:18)
    at Object.<anonymous> (D:\App\sampleIde\\node_modules\@theia\ai-mcp\lib\node\mcp-server.js:19:17)
    at Module._compile (node:internal/modules/cjs/loader:1469:14) {
  code: 'MODULE_NOT_FOUND',
  path: 'D:\\App\\sampleIde\\\node_modules\\@modelcontextprotocol\\sdk\\package.json'
}
Waiting for the debugger to disconnect...

Upon checking, I can confirm that the necessary modules are present in the node_modules folder, as shown in the images below.

On running yarn start, everything works fine, but the issue arises during debugging. It is important for me to debug certain files in order to understand the flow and make necessary changes. This is crucial to move forward with my task. Any suggestions or solutions to resolve this would be greatly appreciated. Thank you

[msujew]

Hey @sowjanyagunupuru,

what does your debug configuration look like?

[sdirix]

@sowjanyagunupuru As @msujew is indicating, please have a look at the debug configurations in Theia. Very likely you are trying to debug the unbundled backend, which then fails to load the ESM module. You need to debug the bundled application.

[sowjanyagunupuru]

Thank you for the suggestion. Here's the current debug configuration I'm using:

{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Start Browser Backend",
"program": "${workspaceRoot}/browser-app/src-gen/backend/main.js",
"args": [
"--loglevel=debug",
"--port=3000",
"--no-cluster",
"--hosted-plugin-inspect=9339",
"--plugins=local-dir:${workspaceRoot}/plugins",
"--basepath=D:/Theia/BaseFolder"
],
"env": {
"NODE_ENV": "development"
},
"sourceMaps": true,
"outFiles": [
"${workspaceRoot}/node_modules/@theia//lib/**/.js",
"${workspaceRoot}//lib/**/.js",
"${workspaceRoot}/browser-app/src-gen/**/*.js"
],
"smartStep": true,
"internalConsoleOptions": "openOnSessionStart",
"outputCapture": "std"
}
]
}
This works perfectly in VSCode version 1.55.0, but when I try to debug with version 1.59.0(upgrade my worksapce from 1.55.0 - 1.59.0 ), it doesn't work as expected. However, running yarn start works fine. The issue is that I want to debug to better understand the flow, but the debugger isn't attaching properly.

I also tried using the launch.json you mentioned from the Theia GitHub repository https://github.com/eclipse-theia/theia/blob/59ea154fad5f60f664cdf8c9992f8764b60daec6/.vscode/launch.json, but that didn't give the desired results either.

Could you kindly suggest any changes I should make to get the debugger working on version 1.59.0? I'd really appreciate your insights on this!

Thank you in advance!

[msujew]

@sowjanyagunupuru As indicated by @sdirix, you're attempting to debug the unbundled app:

${workspaceRoot}/browser-app/src-gen/backend/main.js

You need to replace it with the bundled backend (which is also executed, when you run theia start):

${workspaceRoot}/browser-app/lib/backend/main.js

[sowjanyagunupuru]

Thank you, the issue has been resolved by updating the path. This change has made it much easier to understand the process.

However, I have a small doubt: how did this work in my previous version (1.55.0) using the same path ${workspaceRoot}/browser-app/src-gen/backend/main.js? At that time, I was able to debug using the same launch.json configuration with that path.

[msujew]

how did this work in my previous version?

The dependency in question (@modelcontextprotocol\sdk) that leads to the error, was not included in version 1.55 yet. It was added in a more recent version of the Theia AI packages.

[sowjanyagunupuru]

Thank you for your valuable clarification and for your continued support in helping us resolve these issues. We truly appreciate your assistance.

[sowjanyagunupuru]

I've recently upgraded my Theia-based workspace to version 1.60.2. After successfully running yarn install, yarn prepare, and yarn build, I encountered errors during yarn watch. Additionally, when attempting to start the application, the screen does not load properly as shown in the below image

Following the Theia Windows build instructions, I modified the package.json scripts.

However, when running npm install, I encountered cleanup errors related to EBUSY and EPERM, such as:
EBUSY: resource busy or locked, rmdir ... node_modules\node-pty
EPERM: operation not permitted, rmdir ... node_modules@jest\types

These errors seem related to node-pty, jest, and some @Theia modules.

Failed to remove some directories [
npm warn cleanup [
npm warn cleanup 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\@Theia\process',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules@theia\process\node_modules\node-pty'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\@Theia\process\node_modules\node-pty'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\jest-resolve\node_modules',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\jest-resolve\node_modules@jest\types'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\jest-resolve\node_modules\@jest\types'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\jest-environment-jsdom\node_modules',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\jest-environment-jsdom\node_modules'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\jest-environment-jsdom\node_modules'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\@Theia',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules@theia\plugin-ext\node_modules\node-pty\build\deps\winpty\src\Release\obj\winpty-agent\deps\winpty\src\shared'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'E:\D-Folder\Theia_Upgrade-1.60.0\theia\node_modules\@Theia\plugin-ext\node_modules\node-pty\build\deps\winpty\src\Release\obj\winpty-agent\deps\winpty\src\shared'
npm warn cleanup }
npm warn cleanup ]
npm warn cleanup ]

what steps should i follow either to make npm install or yarn install can succeed? which doesnt effect the screens.
I’d really appreciate any guidance or solutions to get the workspace running smoothly with version 1.60.2.