Promise wrapper on createConnection is problematic in top-level code

The non-promise version of createConnection is not asynchronous. Unlike the database calls, no callback is required here.

var connection = mysql.createConnection({host:'localhost', user: 'root', database: 'test'});

However, the promise wrapper version comes back as a promise.

let connection = await mysql.createConnection({host:'localhost', user: 'root', database: 'test'});

This wouldn't be a problem, except that Node/V8 don't currently allow await outside of an async function, including at the top level of an app. This means that the example code doesn't work when you drop it into a simple Node app. The easy solution that I've come up for this, is to wrap createConnection in an IIFE.

let connection

(async function() {
  try {
    connection = await mysql.createConnection(dbconfig)
  } catch(err){
    console.error(err)
  }
})()

This seems unnecessarily complex, since this isn't a method that needs to be async. I would propose that createConnection remains a synchronous function, the same way it is in the non-promise version. I'm also having difficulty finding an easy way to stick my DB stuff into a module with this pattern.

Start at the createConnection entry point and compare the promise-wrapper behavior with the non-promise version described in the issue. Review the existing discussion and examples first; done means the promise API supports the intended simple top-level Node usage without requiring the proposed IIFE workaround.