pEpForThunderbird/README.md

# p≡p for Thunderbird

## HOW TO BUILD
Using docker

```docker build -t <image_tag> . && docker run -v build:/usr/src/app/build <image_tag> ```
 
Using bash

```zip -r build/pEp4Tb@pEp.security.xpi chrome```

## Check syntax statically

You can parse the code with [Babel](https://babeljs.io/) in order to
catch syntax errors. After installing with `npm install` just run:

    npm run syntaxCheck

## Run ESLint

You can run ESLint to check the style guides defined in `.eslintrc.json` with the npm script:

    npm run lint
    
ESLint can auto fix some problems with the option `--fix` but most of them must be fixed manually:   

    npm run lint --fix
First commit 5 years ago			`# p≡p for Thunderbird`

			`## HOW TO BUILD`
			`Using docker`

			```docker build -t <image_tag> . && docker run -v build:/usr/src/app/build <image_tag> ```
Read files from imap server using streams 4 years ago
			`Using bash`

Change p4t and p4tb to pEp4Tb for chrome:, change preferences to pEp, general cleanup. - Used permanent add-on name in Makefile - Removed unneeded (empty) background.js - renamed p4tb.js to pEpController.js - Added Windows BAT file for zipping up - Fixed Components.interfaces and friends - Removed hacks for TB versions less than 68 3 years ago			```zip -r build/pEp4Tb@pEp.security.xpi chrome```
add a command for static syntax check with babel.js 3 years ago
			`## Check syntax statically`

			`You can parse the code with [Babel](https://babeljs.io/) in order to`
			catch syntax errors. After installing with `npm install` just run:

			`npm run syntaxCheck`
Add how the linter works on the README.md 3 years ago
			`## Run ESLint`

			You can run ESLint to check the style guides defined in `.eslintrc.json` with the npm script:

			`npm run lint`

			ESLint can auto fix some problems with the option `--fix` but most of them must be fixed manually:

			`npm run lint --fix`