- Mozilla Developper Network has a JS guide too.
WHAT DO YOU NEED? HOW TO DEBUG? HOW TO CATCH ERRORS?
First of all, you need to find a way to debug your code and see errors. If your work does not produce any results, you must know why!
Let’s look at this example on JS Bin:
Ok, now, let’s make an error: change console.log() into consollle.log(). Let’s see what happens:
And if we run it standalone and use the dev. tool console:
And if we click on the line number in the right, the dev. tool shows the source code centered on the line that caused the error: