-
Notifications
You must be signed in to change notification settings - Fork 37
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
Nested runAsync
calls throw ReferenceError: Property 'global' doesn't exist
#186
Comments
Actually, shouldn't this Maybe worth mentioning that an |
There were complaints of it working on non releases. This seems to be the only code references that distinguishes the release on the plugin. Possibly the bug is composed around the compacted source map on release versions.
|
Might be related #205 |
When using nested
runAsync
calls like so:The worklet creation throws an error:
- ERROR [ReferenceError: Property 'global' doesn't exist]
For some reason I couldn't reproduce this in this repo, but I can reproduce this 100% / always in react-native-vision-camera.
Funny thing is; this doesn't throw in
context.runAsync(worklet)
, but rather in theconst worklet = () => { ... }
function creation.Maybe it is a bug in the babel plugin?
I think we need two PRs related to this issue btw;
runAsync
sometimes didn't run in release in VisionCamera Frame Processors)The text was updated successfully, but these errors were encountered: