To manage our data loaders, we've been experimenting with storing our data loaders in an "app context" object that's passed around our server-side code.
While circular dependencies may not directly result in bugs, they will almost always have unintended consequences. There are node packages that look for circular dependencies, but
It's possible to extend the default Heroku 30 second timeout by sending meaningless bytes back to the client. This post shows how to do so using Node.js / Express middleware.
I developed a method of logging the queries executed by Knex.js and the execution times for each query. It can be applied to nearly any app that uses Knex.
There's been a lot of effort to add ES6 compatibility to browsers (and Node.js). I'm going to use three Node debugging techniques modified to work with ES6.
