Description

Since Node21, global.navigator has been implemented, and together with browserMock, Benchmark.js incorrectly identifies the execution environment as a browser. It causes error on npm run perf in newer nodejs.
If Benchmark.js is loaded before browserMock, the misidentification will be avoided.

Motivation and Context

I have run npm run perf in some environments and found that the newer nodejs versions have an error.
The problem seemed to be caused by benchmark.js misidentifying the execution environment as a browser.

How Has This Been Tested?

I ran npm run perf on node22 and confirmed that no errors occurred.
Of course, node 18 and 20 do not cause errors. Also, benchmark results should not be affected.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My change requires a documentation update, and I've opened a pull request to update it already:
• I have read https://mithril.js.org/contributing.html.