feat: add USE_OWN_LOCAL_BINARY_PROCESS option to control local binary usage #81
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new configuration option,
USE_OWN_LOCAL_BINARY_PROCESS
, to allow users to use their own BrowserStack Local binary process instead of starting a new one. The changes include updates to the configuration class, conditional logic in the local binary setup, and error handling in the accessibility scanner. Below is a summary of the most important changes:Configuration Updates:
USE_OWN_LOCAL_BINARY_PROCESS
, to theConfig
class insrc/config.ts
, allowing users to specify whether to use their own BrowserStack Local binary process. This is set based on the environment variableUSE_OWN_LOCAL_BINARY_PROCESS
. [1] [2]Local Binary Setup:
ensureLocalBinarySetup
function insrc/lib/local.ts
to skip the setup process ifUSE_OWN_LOCAL_BINARY_PROCESS
is enabled, logging a message to indicate this behavior.Accessibility Scanner:
AccessibilityScanner
class insrc/tools/accessiblity-utils/scanner.ts
to prevent scanning with local URLs whenUSE_OWN_LOCAL_BINARY_PROCESS
is enabled, throwing an error with a clear message.