es7-async | Playing around with ES7 async functions | Reactive Programming library

If you add process.exit(0); right after console.log(`${result} rows inserted.`); the script should exit.

It may be the case it's a connection pool issue, try using destroy like explained here: https://knexjs.org/#Installation-pooling

You are using transactions wrong... try this:

Go to your webpack.dev.config.js and look for entry: []. Just add your runtime.js file there. Like below

The parse error happens in the eslint-loader because the default eslint parser does not understand async and await. You have to use babel-eslint as described in Specifying Parser. In your eslint config add:

but the problem is - await is only allowed in async-methods.

Exactly, and no, there's no workaround for that. JavaScript's run-to-completion semantics demand that synchronous functions complete before any pending asynchronous action (such as the callback to an XHR handler for an async XHR call) can run.

The way JavaScript runs on a given thread is that it processes a queue of jobs¹:

1. Pick up the next pending job
2. Synchronously execute the code for that job
3. Only when that job completes go back to Step 1 to pick up the next job

(It's a bit more complicated than that, there are two levels to it, but that's not relevant to this particular question.)

XHR completions and such are jobs that get scheduled in the queue. There is no way to pause a job, run another job from the queue, and the pick up the paused job. async/await provide dramatically simpler syntax for handling asynchronous operations, but they don't change the nature of the job queue.

The only solution I see for your situation is to go async all the way to the top level. This may not be as complicated as you might think (or maybe it will be). In many cases it's adding async in front of function on a lot of functions. However, making those functions asynchronous is likely to have significant knock-on effects (for instance, something that was synchronous in an event handler becoming asynchronous changes the timing of what happens in relation to the UI).

For example, consider this synchronous code: