@@ -20,13 +20,11 @@ break in /home/indutny/Code/git/indutny/myscript.js:1
20
20
debug>
21
21
```
22
22
23
- Node.js's debugger client does not yet support the full range of commands , but
24
- simple step and inspection are possible.
23
+ Node.js's debugger client is not a full-featured debugger , but simple step and
24
+ inspection are possible.
25
25
26
26
Inserting the statement ` debugger; ` into the source code of a script will
27
- enable a breakpoint at that position in the code.
28
-
29
- For example, suppose ` myscript.js ` is written as:
27
+ enable a breakpoint at that position in the code:
30
28
31
29
``` js
32
30
// myscript.js
@@ -81,8 +79,7 @@ debug> quit
81
79
```
82
80
83
81
The ` repl ` command allows code to be evaluated remotely. The ` next ` command
84
- steps over to the next line. Type ` help ` to see what other commands are
85
- available.
82
+ steps to the next line. Type ` help ` to see what other commands are available.
86
83
87
84
## Watchers
88
85
@@ -95,7 +92,7 @@ To begin watching an expression, type `watch('my_expression')`. The command
95
92
` watchers ` will print the active watchers. To remove a watcher, type
96
93
` unwatch('my_expression') ` .
97
94
98
- ## Commands reference
95
+ ## Command reference
99
96
100
97
### Stepping
101
98
@@ -142,7 +139,7 @@ break in test/fixtures/break-in-module/mod.js:23
142
139
debug>
143
140
```
144
141
145
- ### Info
142
+ ### Information
146
143
147
144
* ` backtrace ` , ` bt ` - Print backtrace of current execution frame
148
145
* ` list(5) ` - List scripts source code with 5 line context (5 lines before and
@@ -171,7 +168,7 @@ An alternative way of enabling and accessing the debugger is to start
171
168
Node.js with the ` --debug ` command-line flag or by signaling an existing
172
169
Node.js process with ` SIGUSR1 ` .
173
170
174
- Once a process has been set in debug mode this way, it can be connected to
171
+ Once a process has been set in debug mode this way, it can be inspected
175
172
using the Node.js debugger by either connecting to the ` pid ` of the running
176
173
process or via URI reference to the listening debugger:
177
174
0 commit comments