If you are using VS Code there is a great debugger tool that hooks in with Chrome to facilate real-time debugging of your code. ![]() In some cases this can even have a performance impact on the production build Let's face it - we have all had / seen this happen. You run the risk of including the logging in a production build. ![]() Descriptive logging helps but as we will see it is not worth the overhead when better options are available. Once you have started putting in a number lines of logging you have to remember where they correspond to in the code. There can end up being so much output that it becomes essentially useless ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |