TypeError: attempted to use private field on non-instance, js engine: hermes

[manufunk]

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 versions of Parse Server and the Parse JS SDK.

Issue Description

If using react native and expo, I receive an error if I do something like const parseQuery = new Parse.Query("Config");.
This happened after upgrading the parse library. It seems that 4.x is affected and also the 5.0.0

Steps to reproduce

I created a sample project that will end up in an error. Just use yarn install and then yarn run start.
I tested on the android emulator via expo app. However same happens on ios.

Actual Outcome

The following error is thrown:

 ERROR  TypeError: attempted to use private field on non-instance, js engine: hermes
 ERROR  Invariant Violation: "main" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called., js engine: hermes

Expected Outcome

No such error.
The sample shows that if switched back to 3.5.1, the error does not appear but it is very old.

Client

• Parse JS SDK version: 5.0.0

Sample for reproduction

example.zip

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[dplewis]

I believe this has been fixed via #2109

Can you try the latest alpha release?