bitwarden-estensione-browser/apps/browser
Robyn MacCallum 8c12ba20cb
[Feature] End User Vault Refresh (#2545)
* Initial org filter work

* update jslib

* Move filter to below cipher length check

* don't show vault filter in personal or org folder

* Use family icon for families org

* jslib and auth guard updates

* lint fixes

* rename GroupingsComponent to VaultFilterComponent

* fix no folder showing all items

* Add checks for PersonalOwnership policy

* update css class names

* lint fixes

* cleanup

* Some final cleanup

* import order lint fix

* remove unused import

* Use smaller icon for chevron

* Update src/popup/vault/organization-filter.component.ts

Co-authored-by: Addison Beck <addisonbeck1@gmail.com>

* Update src/popup/vault/organization-filter.component.ts

Co-authored-by: Addison Beck <addisonbeck1@gmail.com>

* fix lint error

* remove extra localizations

* rename orgFilter -> vaultSelect

* Rename orgFilterService to VaultSelectService

* lint fixes

* combine vault select service with vault filter service

* Use base vault filter service methods

* Use VaultFilter model and other small fixes

* lint fixes

* Final restructuring pass

* Update jslib and remove extra function

* Remove extra imports

* remove space

* Remove vaultFilterService from background services

* Update jslib to latest on feature branch

* merge fix

* update jslib

* [feat] Implement EUVR for desktop

Should contain only https://github.com/bitwarden/desktop/pull/1487, with merge resolutions and style fixes

* [fix] Delete unused GroupingsComponentTemplate

* [dep] Update jslib

Co-authored-by: Addison Beck <addisonbeck1@gmail.com>
2022-05-09 08:19:18 -04:00
..
jslib@141ade3c38 [Feature] End User Vault Refresh (#2545) 2022-05-09 08:19:18 -04:00
src [Feature] End User Vault Refresh (#2545) 2022-05-09 08:19:18 -04:00
store [EC-183] Mono Repository - Browser (#2531) 2022-05-03 19:38:55 +02:00
.gitignore [EC-183] Mono Repository - Browser (#2531) 2022-05-03 19:38:55 +02:00
README.md Rename repo to clients (#2548) 2022-05-05 16:54:48 +02:00
crowdin.yml Crowdin-Pull: Fix paths in browsers crowdin.yml (#2641) 2022-05-06 23:05:59 +02:00
gulpfile.js [EC-183] Mono Repository - Browser (#2531) 2022-05-03 19:38:55 +02:00
karma.conf.js [EC-183] Mono Repository - Browser (#2531) 2022-05-03 19:38:55 +02:00
package-lock.json [EC-183] Move eslint and prettier to project root (#2536) 2022-05-03 21:45:37 +02:00
package.json [EC-183] Move eslint and prettier to project root (#2536) 2022-05-03 21:45:37 +02:00
tsconfig.json [EC-183] Mono Repository - Browser (#2531) 2022-05-03 19:38:55 +02:00
webpack.config.js [EC-183] Mono Repository - Browser (#2531) 2022-05-03 19:38:55 +02:00

README.md

Github Workflow build browser on master Crowdin Join the chat at https://gitter.im/bitwarden/Lobby

Bitwarden Browser Extension

The Bitwarden browser extension is written using the Web Extension API and Angular.

My Vault

Build/Run

Requirements

  • Node.js v16.13.1 or greater
  • NPM v8
  • Gulp (npm install --global gulp-cli)
  • Chrome (preferred), Opera, or Firefox browser

Run the app

npm install
npm run build:watch

You can now load the extension into your browser through the browser's extension tools page:

  • Chrome/Opera:
    1. Type chrome://extensions in your address bar to bring up the extensions page.
    2. Enable developer mode (toggle switch)
    3. Click the "Load unpacked extension" button, navigate to the build folder of your local extension instance, and click "Ok".
  • Firefox
    1. Type about:debugging in your address bar to bring up the add-ons page.
    2. Click the Load Temporary Add-on button, navigate to the build/manifest.json file, and "Open".

Desktop communication

Native Messaging (communication between the desktop application and browser extension) works by having the browser start a lightweight proxy baked into our desktop application.

Out of the box, the desktop application can only communicate with the production browser extension. When you enable browser integration in the desktop application, the application generates manifests which contain the production IDs of the browser extensions. To enable communication between the desktop application and development versions of browser extensions, add the development IDs to the allowed_extensions section of the corresponding manifests.

Manifests are located in the browser subdirectory of the Bitwarden configuration directory. For instance, on Windows the manifests are located at C:\Users\<user>\AppData\Roaming\Bitwarden\browsers and on macOS these are in Application Support for various browsers (for example). Note that disabling the desktop integration will delete the manifests, and the files will need to be updated again.