fix: throw error if BROWSERBASE env is set without API key (fixes #592)

[omlahore]

Fixes #592

why

Previously, the fallback to LOCAL mode was silent, which could be misleading in production. Now, the constructor and getBrowser() both throw informative errors to help developers catch misconfigurations early.

what changed

This PR adds an explicit error when env: "BROWSERBASE" is used without a valid BROWSERBASE_API_KEY.

test plan

Tested with npm run example and verified the error is thrown as expected.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7e42d26

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[greptile-apps]

PR Summary

This PR enforces explicit errors for misconfigured Browserbase environments by throwing informative errors when a BROWSERBASE API key is missing, preventing a silent fallback to LOCAL mode.

• Updated /lib/index.ts to throw explicit errors in getBrowser() when env is "BROWSERBASE" but API key is absent.
• Highlights duplicated API key checks, suggesting consolidation for consistency.
• Improves development feedback by catching misconfigurations early.

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[kamath]

thanks for your contribution! continuing this in #633