Pass-Chrome

Rationale

I love pass (password-store) but I'm tired of having to find the nearest terminal window or opening qtPass and switching windows to use it.

The goal of this project is to bring all the security, control, and awesomeness of pass into the browser, where I find myself needing it most often.

Contributing

####Documentation

####Getting set up

NOTE: this project assumes you have npm and nvm installed

1. Use the correct node version: nvm use to load the correct version from the .nvmrc file

• If you don't have nvm, make sure you're using the version of node that mathces what's in the .nvmrc file

1. Install webpack globally: npm i -g webpack
2. Install project dependencies: npm i
3. Load the extension into chrome:
4. Go to chrome://extensions
5. Ensure the "Developer mode" checkbox is checked

At this point, we need to jump to [running in development...](#running-in-development--workflow) to generate the first build and subsequently the `/dist` directory. Then you can resume from the next step.

1. Click "Load unpacked extension..."
2. Navigate to the /dist directory and click "Select"

At this point you should see the extension in the list and available in the chrome menubar

If you don't see the extension's button check the hamburger menu

####Running in development / Workflow

You can start a build with npm run dev; this watches the filesystem for changes and rebuilds. Once each build is complete you can simply reload in the inspector/console window or form the chome://extensions page to see your changes.

####Building for Production (WIP)

NOTE: not currently implemented

You can build static output by running npm run build; the output is placed in <project root>/build which can then be used as the root for packaging the extension with chrome.