1472542 - DateRangePicker is using node polyfill setTimeout rather than the native browser API

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect, P2)

Description

[Ed Morley [:emorley]]

It currently does:
`import { setTimeout } from 'timers';`

...which means webpack adds the timers-browserify polyfill to the bundle, rather than using the browser's built-in setTimeout. ('timers' is only needed for eg react native apps)

Comment 1

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/4281

Comment 2

[Treeherder GitHub Bugbot]

Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/701e6b0e76f654936c7fc57ba3464d9fcc297ad6
Bug 1472542 - Use native setTimeout rather than via a polyfill (#4281)

The `timers` module is a Node.js built-in, which webpack will polyfill
during the build. Using it adds `timers-browserify` to the bundle
unnecessarily, given that browsers natively support `setTimeout`:
https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout

(This import was presumably copied from a react-native code example.)