We're watching node's support for the webkit developer tools closely but as their recent releases show, integrating with external debugging tools is difficult b

We're watching node's support for the webkit developer tools closely but as their recent releases show, integrating with external debugging tools is difficult because V8 is always a moving target. There are also architectural differences that make it more difficult to offer debugging capabilities in Foxx, such as node being typically run as a single process whereas a typical ArangoDB installation will use any number of parallel V8 threads and incoming requests being load balanced accordingly. We're constantly trying to improve the developer experience of Foxx, though, and the partial rewrite of Foxx for ArangoDB 3.0 was a big part of that, hopefully reducing the need for debugging by making the API easier to reason about. During development I would recommend trying out the development mode and syncing your changes to the deployed service on the file system. For debugging queries it can also be helpful to run them from the web interface first and then use `aql` template strings in JavaScript instead of constructing the queries piece by piece.