You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -180,6 +180,8 @@ absolute path to executable (e.g.:/path/to/iotjs/build/x86_64-linux/debug/bin/io
180
180
After the engine is running you can start the debug session inside the extension host by pressing the `F5` key or click on the green triangle in the debug panel.
181
181
If the client (VSCode extension) is connected then you have to see that file which is running inside the engine or if you started the engine in waiting mode you will get a prompt window where you can select that file what you want to running and then you can see where the execution is stopped. Now you can use the VSCode debug action bar to control the debug session.
182
182
183
+
***Important note:*** When sending multiple sources to debug server, be aware that IoT.js compiles them in the order they are received, so the files containing `require` should be sent first and the files used by them after.
184
+
183
185
***Note:*** If you using the development version of this extension, you have to run the following commands for the first time in the extension directory:
0 commit comments