@bendavis yes it is possible given that your application includes the necessary extensions.
In fact, in the upstream repository we have debug launch configurations to debug the example frontend application for instance:
@vince-fugnitto what are the necessary extensions to enable client-side js debugging? Also, do you mean open-vsx extensions or build-time theia extensions?
@bendavis you will need extensions which provide debug support for whichever languages you require.
In the case of JS/TS the upstream repository has the necessary extensions already for debugging.
In addition, you can reference the theia-apps apps for other examples of setups for different languages.
Also, do you mean open-vsx extensions or build-time theia extensions?
It depends on the language, for JS/TS the builtins (provided by default in VS Code) already support JS/TS debugging. For other languages, external extensions are required (ex:
When I use the launch.json you referenced, it says “chrome” is not a valid type.
@bendavis the example I provided is of course an example, the
chrome type is supported with the following extension (which I include in my VS Code setup): https://open-vsx.org/extension/msjsdiag/debugger-for-chrome.
There is also the following related question:
Ah, I see. Thanks! I will have to experiment with this.
@vince-fugnitto it looks like what I want to achieve is likely impossible. I’m building Theia for use in an educational context. Many students will be using school-issued Chromebooks, and those tend to be locked down with Developer Tools disabled.
With Theia running on a server, I don’t think there’s a way for the debugger to launch an instance of Chrome in “debug mode” (unless I’m mistaken – I’ve tried this with our setup and it doesn’t seem to work). I also can’t expect students to have the access to launch chrome from command-line on their computer with a debug port. So, this rules out using the Debugger for Chrome plugin.