Abstract
Sometimes it's not the writing of code, but the management of it that gets to us, that drives us up a wall and back to our favorite video game. Why does it work on this machine, not that one? What do you mean, double-equals (==) is bad and triple-equals (===) is good? Why is running tests such a hassle? How should I package this code for distribution? We are plagued by questions, distracted by questions that do not directly bear on the code we are writing.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2015 John Resig, Russ Ferguson, and John Paxton
About this chapter
Cite this chapter
Resig, J., Ferguson, R., Paxton, J. (2015). Debugging JavaScript Code. In: Pro JavaScript Techniques. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-6392-0_4
Download citation
DOI: https://doi.org/10.1007/978-1-4302-6392-0_4
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-6391-3
Online ISBN: 978-1-4302-6392-0
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books