Migration Guide to Parse Server 6 issues

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue 1 Description

I am following the migration guide to Parse Server 6, and encountered couple of issues.

I have changed my code to use simpler initialisation:

https://github.com/parse-community/parse-server/blob/76c7a6fbd06693229c1906d68117713bc0a18d42/6.0.0.md?plain=1#L28

And I get the following error:

const api = new ParseServer({...});
            ^

TypeError: ParseServer is not a constructor

I still have to use the old method of const ParseServer = require('parse-server').ParseServer; to get the proper constructor.

Issue 2 Description

Trying to start the parse server in async way via:

await api.start();

Produces the following error:

  await api.start();
  ^^^^^

SyntaxError: await is only valid in async functions and the top level bodies of modules

I have to use the following workaround to actually produce async context on top level of my index.js:

(async function main () {
  await api.start();
})();

Server

• Parse Server version: alpha

Start with the linked 6.0.0.md migration guide at line 28 and compare its ParseServer import with the reported index.js usage. Reproduce both initialization and startup examples in a Parse Server 6 setup; done means the guide's examples use a supported constructor import and valid async startup context.