April 06, 2018
Now we’ve established our code, ooh and if you noticed I’m using the ES5 syntax don’t be scared if you haven’t ported to ES5 you can still use the statement.
Now lets drop in our debugger Statement. The debugger statement is to be put just before the main logic of the function. This is done because as we all know the computer reads from TOP to BOTTOM and from LEFT to RIGHT. So when the computer gets to reading the code and encounters the debugger statement it will because in execution and give us a chance to inspect some of the different variables that is in our program.
This makes it extremely useful for debugging our code or developing and Algorithm solution.
To be able to use the debugger statement in a function, we’ll have to call the function after defining it like so;
If we run this in debugger mode , when the computer reaches the debugger statement it will pause at execution and allow us to inspect the different variables in our code. (I know I’m Repeating myself Goddammit , It’s for ya’ll to understand the key concept).
Now to test our debugger statement we’ll be using a Terminal for those with Linux and Mac-OS you’re safe and for the Windows guys I don’t advice you using the Command Prompt, I advice using the Git Bash (That’s if you haven’t already done it).
Now, Having installed the required things, Head over to your Terminal and make sure you have installed Node.
To go in Debugger mode, Navigate to your working directory and type
cd cd \<your project folder\>
While in your project folder Run
node inspect \<file you want to debug inside the folder\> e.g node inspect index.js
when you’ve run it this should be the output
You see where the debug statement is that’s where we’ll write our commands
So we just Launched that file in Debugger Mode.
To tell the Debugger to Continue Debugging our code you can run the command
Continue //or Cont //or C
If you run the command this should be our output
In the terminal, you will see our entire function displayed and the debugger statement highlighted in Green. That’s how sweet the debugger statement is.
To inspect a variable let’s say the (str), you can’t just write str and expect it to work, if ‘str’ is entered here is what will be displayed
To be able to make this work we’ll have to enter the REPL mode which stands for READ EDIT something something(whatever)!
To enter the REPL mode we run the commamnd
This should be the output
Typing str should bring out ‘asdf’ because we assigned asdf as our str in our code.
Now what if we Put in the main logic of our function i.e we reverse the string ‘asdf’ , if our function works, it will return ‘fdsa’ so lets try it out . If i copy
str.split('').reduce((rev, char)=\> char + rev, '');
and paste it in the repl console it should return the reversed string like this
Remember to copy and paste in a terminal is
ctrl + Alt + C //Copy ctrl + Alt + V //Paste
To leave REPL mode and go back to debug mode hit Ctrl + C
When in debug mode we’ll run the code again just to show us another issue .
In a single session the debugger can run for as many times as where the debugger statement appears
Since i assigned it in only one function this is the output when put in C
It shows just that message because there is no Debugger statement in our Code.
To Leave the Debugger type _ exit_
Hi me on twitter to say HI! or Ask a Question.