4 fork work fix browserautherror crypto nonexistent for firefox upstream issue 8391

[Christopher-C-Robinson]

Purpose

Fix BrowserAuthError: crypto_nonexistent behavior reported in #8391 for Firefox runs in proxy mode (--disable-native-automation), and add regression coverage.

Approach

• Bumped testcafe-hammerhead to include the upstream fix used by TestCafe client/proxy injection.
• Added a regression fixture for Getting a 'BrowserAuthError: crypto_nonexistent: The crypto object or function is not available' error when using testcafe with firefox #8391:
  • test/functional/fixtures/regression/gh-8391/test.js
  • test/functional/fixtures/regression/gh-8391/testcafe-fixtures/index.js
  • test/functional/fixtures/regression/gh-8391/pages/index.html
• Regression intent: verify TestCafe client scripts initialize correctly in Firefox proxy mode and avoid the broken runtime path that leads to missing crypto/auth errors.

References

• Getting a 'BrowserAuthError: crypto_nonexistent: The crypto object or function is not available' error when using testcafe with firefox #8391

Validation

• gulp test-server (local): 809 passing, 1 pending, 3 failing
• Failures are local-environment related and tied to macOS Screen Recording API access:
  • Runner .src() -> Should accept source files in different forms
  • Runner Regression -> Should not have unhandled rejections in runner (GH-825)
  • Runner after all hook ...
  • error: UnableToAccessScreenRecordingAPIError: The find-window process cannot access the Screen Recording API
• Focused runner check passes:
  • npx mocha test/server/runner-test.js --timeout 120000 --grep "permission|retry|_checkRequiredPermissions"
  • result: 3 passing

Pre-Merge TODO

• Write tests for your proposed changes
• Make sure that existing tests do not fail (blocked locally by macOS Screen Recording permission/TCC behavior)

[Copilot]

Pull request overview

This PR addresses a Firefox proxy-mode (--disable-native-automation) initialization failure (BrowserAuthError: crypto_nonexistent, #8391) by ensuring TestCafe uses a localhost hostname strategy when all target browsers are local, and adds regression coverage around the scenario.

Changes:

• Update proxy bootstrap flow to detect when all browsers are local and pass that signal into hostname calculation.
• Extend hostname calculation logic to prefer localhost for proxy mode when hostname is unset and all browsers are local.
• Add/extend server- and functional-level regression tests for GH-8391 and the new hostname strategy.

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/runner/bootstrapper.ts	Computes allBrowsersLocal and feeds it into hostname calculation during proxy setup.
src/configuration/testcafe-configuration.ts	Adds allBrowsersLocal support to hostname calculation to select localhost in proxy mode when appropriate.
test/server/configuration-test.js	Adds unit coverage for the new hostname calculation branch.
test/server/bootstrapper-test.js	Adds a unit test asserting proxy setup uses the localhost hostname strategy for local browsers in proxy mode.
test/functional/fixtures/regression/gh-8391/*	Adds a functional regression fixture + page for Firefox proxy-mode initialization.
package-lock.json	Lockfile refresh reflecting dependency updates (incl. testcafe-hammerhead).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

_isAllBrowsersLocal calls browser.provider.isLocalBrowser(void 0, ...) for every BrowserInfoSource. When the entry is a BrowserConnection, an id is available (browser.id) and some providers rely on it to determine locality; passing undefined risks misclassifying remote connections as local, which can incorrectly force hostname to localhost in proxy mode. Pass the connection id for BrowserConnection instances (and keep undefined for plain BrowserInfo).

[Copilot]

This regression test is intended to verify Firefox behavior specifically in proxy mode (--disable-native-automation), but it doesn’t enforce that mode. Since the functional test harness can run with NATIVE_AUTOMATION=true, this test may execute in native automation and fail to cover the reported scenario. Please skip/guard this test when config.nativeAutomation is true (or explicitly run with disableNativeAutomation: true in this test).

Suggested change

	return runTests('testcafe-fixtures/index.js', 'Should run a simple assertion in Firefox proxy mode', { only: 'firefox' });
	return runTests('testcafe-fixtures/index.js', 'Should run a simple assertion in Firefox proxy mode', { only: 'firefox', disableNativeAutomation: true });