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
`IoT.js Debug` is a debugger extension for [Visual Studio Code](https://code.visualstudio.com/) that lets you debug the code which is running on a device and lets you upload your code to the device, directly from the VSCode over websocket communication.
12
+
`IoT.js VSCode Extension` is a debugger and language (like intelliSense, hover, ...) extension for [Visual Studio Code](https://code.visualstudio.com/) that lets you debug the code which is running on a device, lets you upload your code to the device, directly from the VSCode over websocket communication and helps you to write code with [IoT.js](https://github.com/Samsung/iotjs).
13
13
14
14
# Features
15
-
Available Control commands:
16
-
- Continue command
17
-
- Pause command
18
-
- Step-over command
19
-
- Step-in command
20
-
- Step-out command
21
-
- Disconnect command
22
-
23
-
Available features:
24
-
- Set/Remove breakpoint
25
-
- Call stack display
26
-
- Watch (evaluate expression)
27
-
- Handle source receive from the engine
28
-
- Sending source code from the vscode to the engine
29
-
30
-
Currently in Progress features or commands:
31
-
- IoT.js module based completion
15
+
- Debugger
16
+
- Available Control commands:
17
+
- Continue command
18
+
- Pause command
19
+
- Step-over command
20
+
- Step-in command
21
+
- Step-out command
22
+
- Disconnect command
23
+
24
+
- Available features:
25
+
- Set/Remove breakpoint
26
+
- Call stack display
27
+
- Watch (evaluate expression)
28
+
- Handle source receive from the engine
29
+
- Sending source code from the vscode to the engine
32
30
33
31
# Requirements
34
32
- The latest Vscode which is available [here](https://code.visualstudio.com/Download).
35
33
- An [IoT.js](https://github.com/Samsung/iotjs) or a [JerryScript](https://github.com/jerryscript-project/jerryscript) as an engine to run your code.
36
34
37
35
- (For development) Requires [node.js](https://nodejs.org/en/) v8.x.x or higher (latest one is recommended) and [npm](https://www.npmjs.com) 5.x.x or higher to be able to work properly.
Use the proper node.js and node package manager version:
61
-
```sh
62
-
# Install the latest node.js and npm with the nvm tool
63
-
$ nvm install 9
64
-
65
-
# If you have already installed the node.js and npm then make sure you are using the right version in the project folder
66
-
$ nvm use 9
67
-
```
68
-
69
-
Install the project dependencies:
70
-
```sh
71
-
npm install
72
-
```
73
-
74
-
For the first time you have to build the project to be able to start the extension host, this will build the project into the `out` folder:
75
-
```sh
76
-
npm run compile
77
-
```
78
-
79
-
To start the extension you have to open the project in VSCode and you have to navigate to the Debug view (Ctrl+Shift+D).
80
-
At the top of the debug panel you have to select the `Extension` option from the dropdown menu if you want to run the extension (or you have to select the `Extension Test` if you want to run the unit tests).
81
-
After you selected the `Extension` option you can start the debug session by pressing the `F5` key or click on the green triangle shaped button next to the dropdown menu.
82
-
This debug session will open up a new VSCode (Extension host) where our extension is installed and available.
83
-
84
-
**Note:** When the extension host window is opened you do not have to rebuild the project if you make any changes on the code because vscode will automatically do that, the only thing you have to do is restart the main debug session in the main vscode window by hit the restart button in the debug action bar or press the Ctrl+Shift+F5 key combination.
85
-
86
37
# How to use
87
-
After the extension is running in the extension host window you have to open (or create a new) project folder where you have to define a `launch.json` configuration file inside the `.vscode` folder. In case of IoT.js Debug this configuration looks like this:
38
+
You have to open (or create a new) project folder where you have to define a `launch.json` configuration file inside the `.vscode` folder. In case of IoT.js Debug this configuration looks like this:
88
39
89
40
```json
90
41
{
@@ -98,7 +49,7 @@ After the extension is running in the extension host window you have to open (or
0 commit comments