59754cd530
* TypeScript and WebPack. * Minor cleanup. * Add background.js as entry point to webpack. * Use downloaded fonts for better performance. Remove google-fonts-webpack-plugin. * Add the remaining entry points and setup notification bar. * Update readme for webpack. * Convert CipherItems to TypeScript to demonstrate how a component looks in TS. * Fix edge requirering a custom angular version. * Rewrite gulp tasks for packaging releases. * Re-add the webpack gulp plugin. * Remove unessesary line in analytics. |
||
---|---|---|
src | ||
store | ||
.editorconfig | ||
.gitignore | ||
bitwarden-browser.sln | ||
CONTRIBUTING.md | ||
crowdin.yml | ||
gulpfile.js | ||
LICENSE.txt | ||
package.json | ||
README.md | ||
SECURITY.md | ||
tsconfig.json | ||
webfonts.list | ||
webpack.common.js | ||
webpack.dev.js | ||
webpack.prod.js |
bitwarden Browser Extension
The bitwarden browser extension is written using the Chrome Web Extension API and AngularJS.
Build/Run
Requirements
By default the extension is targeting the production API. If you are running the Core API locally, you'll need to switch the extension to target your local instance. Open src/services/apiService.js
and set self.baseUrl
and self.identityBaseUrl
to your local API instance (ex. http://localhost:5000
).
Then run the following commands:
npm install
gulp build
npm run dev:watch
You can now load the extension into your browser through the browser's extension tools page:
- Chrome/Opera:
- Type
chrome://extensions
in your address bar to bring up the extensions page. - Enable developer mode (checkbox)
- Click the "Load unpacked extension" button, navigate to the
dist
folder of your local extension instance, and click "Ok".
- Type
- Firefox
- Type
about:debugging
in your address bar to bring up the add-ons page. - Click the
Load Temporary Add-on
button, navigate to thedist/manifest.json
file, and "Open".
- Type
Contribute
Code contributions are welcome! Please commit any pull requests against the master
branch. Learn more about how to contribute by reading the CONTRIBUTING.md
file.
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.