👷 Load BrowserStack credentials from .env file

[thomas-lebeau]

Motivation

BrowserStack credentials (BS_USERNAME and BS_ACCESS_KEY) currently need to be manually exported as environment variables before running BS tests. This is error-prone and credentials can accidentally end up in shell history.

Changes

• Add --env-file-if-exists=.env flag to test:unit:bs and test:e2e:bs scripts so Node.js automatically loads variables from a .env file when present
• Add .env* to .gitignore (with !.env.example exception) to prevent credential leaks
• Add .env.example documenting the expected variables

This is fully opt-in — exporting env vars manually as before still works. The .env file is only loaded if it exists (--env-file-if-exists).

1Password Environments

For a more secure setup, you can use 1Password Environments to manage the .env file. 1Password can mount the file on the filesystem on demand and will ask for permission before

Test instructions

1. Create a .env file at the repo root with your BrowserStack credentials:

   BS_USERNAME=your_username
   BS_ACCESS_KEY=your_key
   

2. Run yarn test:unit:bs or yarn test:e2e:bs — credentials should be loaded automatically
3. Verify the .env file is not tracked by git (git status should not show it)

Checklist

• Tested locally
• Tested on staging
• Added unit tests for this change.
• Added e2e/integration tests for this change.
• Updated documentation and/or relevant AGENTS.md file