Click any tag below to further narrow down your results
+ devtools
(3)
+ memory-profiling
(1)
+ performance
(1)
+ error-tracking
(1)
+ development
(1)
+ software-engineering
(1)
+ circular-dependencies
(1)
+ programming
(1)
+ software-development
(1)
+ chrome
(1)
+ web-development
(1)
+ source-maps
(1)
+ encoding
(1)
+ memory-inspection
(1)
+ api-testing
(1)
Links
Wirebrowser is a toolkit that combines network manipulation, API testing, and JavaScript memory inspection using the Chrome DevTools Protocol. It features live object search, heap snapshot analysis, and real-time HTTP request interception, making it useful for developers and researchers in debugging and reverse engineering applications.
This article explains how source maps link minified JavaScript code back to its original source, making debugging easier. It details the structure of source maps, the encoding methods used, and how tools like DevTools utilize them to provide developers with meaningful error information.
This article highlights three lesser-known features of Chrome's DevTools, including how to time functions, watch DOM elements for changes, and attach listeners to functions. These tips aim to enhance debugging and development efficiency.
Circular dependencies in JavaScript can lead to issues such as unexpected behaviors and difficulties in debugging. The article explores the causes and consequences of circular dependencies, as well as strategies to identify and resolve them effectively. Understanding these dependencies is crucial for maintaining clean and efficient code in JavaScript applications.
The article discusses the need for debug IDs in JavaScript to enhance the debugging process. It emphasizes that such identifiers can significantly improve error tracking and make it easier for developers to resolve issues in their code. By implementing debug IDs, developers can gain more context around errors, leading to quicker resolutions and better overall code quality.
A technique is presented to find where a specific object was allocated in JavaScript using Chrome DevTools' memory profiler. By profiling allocations and purposefully leaking the object as a global variable, developers can easily track down the object's creation point in the stack trace. This method is particularly useful when dealing with complex codebases or obscured stack traces.