You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Switch from hardcoded `window.performance` to `performance` as global
more generally, so it works in Node.js as well.
Note by default this remains only enabled in browsers, as controlled
by `src/core/start.js` where we check:
```
if (config.reporters.perf || (config.reporters.perf === undefined && window && document)) {
```
So this change does not start enabling it in Node.js. But, you can now
enable it on Node.js via `qunit_config_reporters_perf=true` or by
invoking `QUnit.reporters.perf.init(QUnit)`, which previously did not
do anything on Node.js.
Copy file name to clipboardExpand all lines: docs/api/reporters/perf.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,8 +19,8 @@ This uses the [performance.measure()](https://developer.mozilla.org/en-US/docs/W
19
19
QUnit enables the perf reporter by default in [Browser](../../browser.md) environments. The measures are automatically included in Firefox Profiler and Chrome DevTools (Safari is pending [WebKit #213870](https://bugs.webkit.org/show_bug.cgi?id=213870)).
0 commit comments