Evidently debugging NodeWebKit applications requires that you download the full Chromium source and compile the developer build from scratch. This is time consuming as the repository clocks in at a whopping 5.24 GB and requires additional toolchains and Python libraries for compilation.
Additionally, the repository requires Chromium Depot Tools to build - installation instructions can be found here: Chromium Depot Tools
Aside from documenting the debugging process it might make sense to sandbox the development environment in a VM. Furthermore, downloading the Chromium source code is incredibly time consuming so we may want to explore the option of hosting a private mirror for our own development purposes.
Evidently debugging NodeWebKit applications requires that you download the full Chromium source and compile the developer build from scratch. This is time consuming as the repository clocks in at a whopping 5.24 GB and requires additional toolchains and Python libraries for compilation.
Build instructions can be found here: Building NW.js
Additionally, the repository requires Chromium Depot Tools to build - installation instructions can be found here: Chromium Depot Tools
Aside from documenting the debugging process it might make sense to sandbox the development environment in a VM. Furthermore, downloading the Chromium source code is incredibly time consuming so we may want to explore the option of hosting a private mirror for our own development purposes.