Whenever your NodeGui application is not behaving the way you wanted it to, an array of debugging tools might help you find coding errors, performance bottlenecks, or optimization opportunities.
Since a NodeGui application runs on Qode. And Qode is essentially NodeJs. We can consider a NodeGui app as a regular NodeJs app. Hence, you can use any debugging tool that you use with NodeJs One of the most popular ways of debugging a NodeJs app is by making use of the Chromium Developer Tools.
Google offers excellent documentation for their developer tools. We recommend that you make yourself familiar with them - they are usually one of the most powerful utilities in any NodeGui Developer's tool belt.
Debugging Qode process
launch Qode with the
--inspect-brk switch. Once you run it you can open up Chrome and visit
chrome://inspect where you should see your app listed.
Command Line Switches
Use one of the following command line switches to enable debugging of the process:
Qode will listen for V8 inspector protocol messages on the specified
an external debugger will need to connect on this port. The default
If you are using the official boilerplate
nodegui-starter, then you can achieve this by running
You will need to use a debugger that supports the V8 inspector protocol.
- Connect Chrome by visiting
chrome://inspectand selecting to inspect the launched NodeGui app present there.
- Debugging the NodeGui app in VSCode