* [PM-43929] Exclude core-js polyfills from Chrome extension build (#23433) * [PM-43929] Exclude core-js polyfills from Chrome extension build The Chrome Web Store flags core-js's IE-era Object.create shim (ActiveXObject and a hidden-iframe javascript: trick) as obfuscated code. Modern Chrome (auto-updating, floor 134+) natively provides Object.create and explicit resource management (using, Symbol.dispose, DisposableStack), so the Chrome build can ship without the core-js/stable and core-js/proposals/explicit-resource-management imports. Firefox (AMO) and Safari (App Store) keep them; older Safari still lacks native explicit resource management. Implemented as a NormalModuleReplacementPlugin keyed on the BROWSER env var, so source files are unchanged and only the Chrome artifact is affected. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * doc: fix AI comment * [PM-43929] Pin Chrome build to Chrome 134 minimum The Chrome build drops the core-js polyfills that supply Symbol.dispose and explicit resource management, which the SDK's `using ref = sdk.take()` disposal (a core vault-decrypt path) relies on. Chrome provides these natively from 134, but the manifest still declared minimum_chrome_version 102.0, so the Web Store could serve this build to Chrome 102 through 133, where the downleveled `using` helper throws "Symbol.dispose is not defined". Pin minimum_chrome_version to 134 for the Chrome build via a __chrome__ manifest override, so Edge and Opera (which keep core-js) stay at 102. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * [PM-43929] Require Chrome 134 for all Chromium builds Raise minimum_chrome_version to 134 for every Chromium-based build (Chrome, Edge, Opera), matching the native Symbol.dispose and explicit-resource-management support the SDK's `using` disposal relies on, in place of the chrome-only override. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Bumped client version(s) (#23461) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Bumped client version(s) (#23465) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --------- Co-authored-by: Andreas Coroiu <acoroiu@bitwarden.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bitwarden Client Applications
This repository houses all Bitwarden client applications except the mobile applications (iOS | android).
Please refer to the Clients section of the Contributing Documentation for build instructions, recommended tooling, code style tips, and lots of other great information to get you started.
Related projects:
- bitwarden/server: The core infrastructure backend (API, database, Docker, etc).
- bitwarden/ios: Bitwarden iOS Password Manager & Authenticator apps.
- bitwarden/android: Bitwarden Android Password Manager & Authenticator apps.
- bitwarden/directory-connector: A tool for syncing a directory (AD, LDAP, Azure, G Suite, Okta) to an organization.
We're Hiring!
Interested in contributing in a big way? Consider joining our team! We're hiring for many positions. Please take a look at our Careers page to see what opportunities are currently open as well as what it's like to work at Bitwarden.
Contribute
Code contributions are welcome! Please commit any pull requests against the main branch. Learn more about how to contribute by reading the Contributing Guidelines. Check out the Contributing Documentation for how to get started with your first contribution.
Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md file.
