ReferenceError: requestAnimationFrame is not defined

[nDeavor9]

Description

I'm using Expo SDK 49 with Router v2 and when I enable static output and export web using metro bundler, I get this error:
ReferenceError: requestAnimationFrame is not defined at JSReanimated.scheduleOnUI

This issue talks about it and this PR is what I think is initiated to solve this issue.

But it's been a month since the PR is opened and no moves are made on it yet.

If there's any work around I can do till then, please suggest. Thank you.

P.S: I'm not attaching any snack link because this issue doesn't appear during local runtime and can only be reproducible if we export it.

Steps to reproduce

1. Install expo 49 with expo router v2.
2. Use drawer from expo-router/drawer.
3. Set bundler as 'metro' and output as 'static' in app.json.
4. Try exporting it using npx expo export --platform web

Snack or a link to a repository

N/A

Reanimated version

3.3.0

React Native version

0.72.3

Platforms

Android, iOS, Web

JavaScript runtime

None

Workflow

None

Architecture

None

Build type

None

Device

None

Device model

No response

Acknowledgements

Yes

[github-actions]

Hey! 👋

The issue doesn't seem to contain a minimal reproduction.

Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem?

[nDeavor9]

@piaskowyk Sorry for tagging directly. Can you please look into this? It's urgent.

[heythisischris]

I'm also experiencing this issue- would appreciate any help!

[awilson9]

Have a minimum reproducible example here: expo/expo#23412 (comment)

It's the same error message (ReferenceError: requestAnimationFrame is not defined)

No idea if it's related but definitely feels like it is

[mamatsunami]

I had exactly the same issue but on Next.js.

Don't know why, but moving import "raf/polyfill"; from _app.tsx to _document.tsx fixed the issue on my app.

[piaskowyk]

Should be solved by #4665

This fix is available since 3.5.0