Summary

There is much to add on the subject of debugging for NW.js. As stated in the introduction, NW.js is very powerful but also pretty young. Depending on the release you pick for deploying your application, you might stumble on bugs or a lack of implementations that could drive you crazy.

That's why the issues page exists (https://github.com/nwjs/nw.js/issues), with more than 1,700 closed issues but over 1,000 still open.

Also, to address these kinds of issues, from version 0.8, NW.js supports Crash dumps. I haven't dived deep into the argument as I find it a bit too much for the purpose of the book. However, feel free to learn more about it at https://github.com/nwjs/nw.js/wiki/Crash-dump.

We're almost done. In the last chapter, we're going to see the subsequent steps and list resources and tools for you to keep learning about NW.js.