Let’s start by attaching the official definition of ndb: Well, it’s cool there is another way to debug a Node.js application - but what’s the point of an additional debugging tool? □ Motivation Perhaps you’ve heard that on July 20th - a new tool called ndb was released as an open source project! □ Connecting it to a Chromium-based browser is pretty simple - we just had to navigate to the output URL of the command: node -inspect script.js. Thus, it could be connected with inspector clients, for instance - a Chromium-based browser, VSCode, WebStorm/IntelliJ. Furthermore, it didn’t depend on the deprecated V8 debugger protocol, rather the Chrome Debugging Protocol. It was very useful because we could benefit from some DevTools capabilities.Īs part of Node.js v6.3.0, a new experimental feature came out - the V8 inspector, which brought a much powerful debugging protocol that integrates with Chrome DevTools and supports up-to-date features like blackboxing, profiling, workspaces, source maps and more. This tool enabled us to debug our Node.js application through the DevTools of a WebKit-based browser such as Chrome and Opera! Yes, we’re talking about node-inspector. It was based on the V8 debugger protocol and the developer tools of Blink (the Webkit-based rendering engine of Chromium). Over the years, an improved debugging tool showed up. This native tool wasn’t a full-featured debugger, but enabled simple inspections. It used a deprecated protocol, which was called V8 debugger protocol. As some of you might remember, a headless native debugging tool was supported in Node.js for a long time: Demonstrating the native Node.js debugger
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |