![]() ![]() Well, we haven’t noted anything about the dependencies of ndb yet, so that’s a good time - ndb depends (among other things) on a very popular package, which is called Puppeteer. What if we prefer using other browsers on daily basis or just prefer to not install a Chromium-based browser, but still want to be able to debug a Node.js application regardless of our editor? Obviously, the V8 inspector and Chrome DevTools integration assumes that two fundamental things are installed: Node.js v6.3.0+ and a Chromium-based browser. So you might think that ndb just enables extra features compared to the V8 inspector - however that’s not completely the case. ndb is part of Google Chrome Labs and maintained by the Google Chrome team.ndb is based on Chrome DevTools, which means it uses the Chrome Debugging Protocol, similar to the V8 inspector.ndb improves the debugging experience by providing an easier workflow and exclusive capabilities.Ndb is an improved debugging experience for Node.js, enabled by Chrome DevToolsįrom the definition above, we can presume implicitly that: 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 |