browser-automation / cba

Chromium Browser Automation (extension for chrome browser automation).

Chromium browser automation

Browser extension for automating chromium browser with more than 43 000 weekly users and 250 000 downloads.

• Stable version: https://chrome.google.com/webstore/detail/chromium-browser-automati/jmbmjnojfkcohdpkpjmeeijckfbebbon
• Website: https://chrome-automation.com
• Documentation: https://chrome-automation.com/documentation
• Tutorials: https://chrome-automation.com/tutorial

Check out the blog post about rewriting CBA, to learn more about why CBA was created, what is new and what are our future plans for the project.

Installation

npm install

Setting up development environment

• Run one of the commands below

npm run build:webpack       # builds extension in `dist` directory
npm run build:webpack:watch # builds extension and watches for changes 
build:webpack:prod          # builds production version with minified files

• Visit chrome://extensions in your browser
• Ensure that the Developer mode checkbox in the top right-hand corner is checked
• Click Load unpacked button
• Locate and load generated dist folder in the repository root directory

Note: When rebuilding the extension changes in background scripts might not be loaded in the chrome unless actual extension is reloaded in the chrome://extensions page (i.e. By clicking on the reload button).

Testing

npm test                # Run puppeteer test
npm run test:pages      # Starts server with test page used by puppeteer
npm run lint            # Run linter

Publishing

Command below bundles the extension into cba.zip file:

npm run build

Wiki

https://github.com/browser-automation/cba/wiki

Installing CBA 8.3.7

After release of 9.0.0 several users reported CBA being broken, that is most probably because of the current issue. Until the mentioned issue is fixed you can downgrade to the old version of CBA by following current steps.

Contribution

Reporting bugs, suggestions and questions

Use Github issue tracker for requesting features, reporting bugs and questions. See github issues documentation.

Code contribution

Code contributions are welcome, you can always consult with me (in issues, or PRs) when you have a question. If you are developing a new feature, please consider creating also tests for them when possible.

Website changes

Please refer to the website repository for contributions referring to the chrome-automation.com content, layout and/or styles.

Thanks to the awesome contributors

• @naarrek
  • For migrating chrome-automation.com from Drupal instance to CMintS and implementing all necessary changes for that.
  • For helping with testing Beta version of CBA.