Manuel

Restarted CI

I've resolved the conflicts, waiting for CI to pass

Not sure how to handle this change of which is essentially a 3rd party-managed API. This is a clear example of why https://github.com/parse-community/parse-server/issues/7979 is so important to move GraphQL into...

@dblythy Is this ready for review?

That would be great, also see https://github.com/parse-community/minami/pull/1#issuecomment-1140267604 why I would rather not touch the current template.

Right, can we then point to the original dependency (rather than maintaining our own fork) and just add a config file to each repo?

We'd need to make sure that all content is included in the new template; @dblythy [mentioned](https://github.com/parse-community/parse-server/issues/8017#issuecomment-1140273411) that there was some customization in the old template.

To clarify for reviewers, this PR intents to upgrade a dependency and switch from promisify to async/await. Bumping the min Node.js requirement is merely a side effect, but it makes...

Thanks for the update, let's leave this open for now, if someone wants to pick this up.

> ## ⚠️ Important change for merging PRs from Parse Server 5.0 onwards! > > We are planning to release the first beta version of Parse Server 5.0 in October...