![]() Unfortunately, it’s a terrible debugging utility and you shouldn’t use it. It’s often the first debugging method taught to JS newbies it’s concise, easy to understand, and provides immediate feedback. I don't use Safari much, though, so I'll let someone else write that blog post □□□ alert(): not even onceĪlert(value) pops up a browser-level modal containing value. PPS, Safari also has a built-in debugger with a really similar feature set. PS, you can 100% use the Chrome debugger on backend JS as well - check out the very end of this post. I'll run over what they are and why two of them fall short. There are three major options for debugging frontend JavaScript. So if I just found about the debugger, how have I been debugging code until now? Hope it'll make your lives easier! □ The debugging landscape ![]() It's high time to pay this forward, so here's a primer on the Chrome debugger. I can isolate behavior, test out ideas, and feel my way around the codebase more quickly and reliably than ever before. Learning how to use the Chrome debugger helps me write and debug more quickly, but more than just that, I actually understand code better. Since then, it's been my go-to aide for everything JavaScript.Īctual photo of someone using the Chrome debugger. Yep, I was surprised, too - I didn't even realize it existed for years. The best tool for doing all of this has been Google Chrome's built-in debugger. How can I build out functionality more quickly? How can I understand my code better? How can I debug more reliably? I'm always on the lookout for ways to make my job easier.
0 Comments
Leave a Reply. |