FAQ: Debugging JavaScript Code - Reading Error Stack Traces

This community-built FAQ covers the “Reading Error Stack Traces” exercise from the lesson “Debugging JavaScript Code”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Web Development

FAQs on the exercise Reading Error Stack Traces

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

Are there any particular tools to debug JavaScript code or ways to debug JavaScript code in some text editors say Atom or Visual Studio Code?

Debugging is a manual process. The two most important tools are the error trace, and the writer’s ability to understand it enough to trace down both the error and its possible cause(s).

Many errors are typographical, in which case most editors will have a linting tool that usually runs in the background and flags lines that raise a question as to their composition. Editors may also have syntax highlighting which gives some indication of where an omission may have occurred, such as a missing quote mark, or some other delimiter such as a bracket or a brace is missing.

Practice is about the only way a writer becomes proficient at tracking down and fixing errors. Since a program could not know with any certainty what the objective of the writer is, it would be presumptuous to perform any changes purely on the basis of syntax so one can see why the writer is so important in the debugging process.