setTimeout execute immediately at 1e12; This causes useRaf not working.

[cnwangjie]

What is the current behavior?

useRaf not working at the default. After some testing, I found setTimeout execute immediately at 1e12.

https://codesandbox.io/s/silly-shadow-0vq5c?fontsize=14&hidenavigation=1&theme=dark

What is the expected behavior?

A little about versions:

• OS: macOS Mojave
• Browser (vendor and version): Chrome 80.0.3968.0
• React: any version
• react-use: 13.8.0

[thoamsy]

Maybe the browsers just throttle down the 1e12 to 0 or something else. Like the below code, you can see 10, 20, 30.

setTimeout(() => console.log(20), 1);
setTimeout(() => console.log(30), 1e12)
console.log(10)

I think you can use it with useRaf(50) instead of useRaf()

[xobotyi]

Whole JS setTimeout and setInterval does not work with numbers greater than 1e12(actually 2147483647) , because they use 32bit integer inside. https://stackoverflow.com/questions/3468607/why-does-settimeout-break-for-large-millisecond-delay-values