mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-09-30 01:07:01 +08:00
Lorne Mitchell
db3885dd80
This reverts commit 4df552c652.
Reason for revert: Breaks esprima.
Original change's description:
> Updates node_modules and update script
>
> Change-Id: I3fcf49bc416301a030d298cfc48c448bfeba4335
> Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1878808
> Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org>
> Reviewed-by: Yang Guo <yangguo@chromium.org>
> Commit-Queue: Paul Lewis <aerotwist@chromium.org>
TBR=yangguo@chromium.org,aerotwist@chromium.org,tvanderlippe@chromium.org
Change-Id: Iad2bcdf98a486476715d1e829cdce450c5f218af
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1880098
Reviewed-by: Lorne Mitchell <lomitch@microsoft.com>
Commit-Queue: Lorne Mitchell <lomitch@microsoft.com>
Overview
Adds support for the timers module to browserify.
Wait, isn't it already supported in the browser?
The public methods of the timers module are:
setTimeout(callback, delay, [arg], [...])clearTimeout(timeoutId)setInterval(callback, delay, [arg], [...])clearInterval(intervalId)
and indeed, browsers support these already.
So, why does this exist?
The timers module also includes some private methods used in other built-in
Node.js modules:
enroll(item, delay)unenroll(item)active(item)
These are used to efficiently support a large quantity of timers with the same timeouts by creating only a few timers under the covers.
Node.js also offers the immediate APIs, which aren't yet available cross-browser, so we polyfill those:
setImmediate(callback, [arg], [...])clearImmediate(immediateId)
I need lots of timers and want to use linked list timers as Node.js does.
Linked lists are efficient when you have thousands (millions?) of timers with the same delay. Take a look at timers-browserify-full in this case.