-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration Guide to Parse Server 6 issues #8383
Comments
Thanks for opening this issue!
|
Which Node version are you running? await on top level is unflagged since Node 14.8.0. |
@mman I followed the migration guide and the directions worked for me. Your error seems to be related to how you are calling your async method. My updated code is here for reference: https://github.com/netreconlab/parse-hipaa/blob/89ccb02db7970ffd494a1dae907f9a660e117171/parse/index.js#L407-L409. I used the As far as your first issue, I still used the old way as well... |
@cbaker6 Looks like you are calling |
@mtrezza This is happening for me on Node 16. |
New Issue Checklist
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:
parse-server/6.0.0.md
Line 28 in 76c7a6f
And I get the following error:
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:
Produces the following error:
I have to use the following workaround to actually produce async context on top level of my
index.js
:Server
The text was updated successfully, but these errors were encountered: