This extension can help you development on Gerrit sites, frontend specifically
Gerrit FE Dev Helper Extension
source: https://gerrit-review.googlesource.com/q/project:gerrit-fe-dev-helper''
## v1
#### v1.1.0
- Remove support for INJECT_JS_PLUGIN and INJECT_JS_MODULE_PLUGIN.
Content Security Policy for extensions does not allow injecting arbitrary JS.
#### v1.0.2
- Fix injecting JS plugins, remove webcomponents-lite.js
#### v1.0.1
- Fix rules to also work with non-Google hosted Gerrit
- Add a `inject css` rule
- P1 fix: Continue rules processing after first disabled one
#### v1.0.0
- Migrate to Manifest V3
- Restrict the permissions to only run on a specific list of hosts
- Migrate the background script to a service worker
- Migrate request/response manipulation to `chrome.declarativeNetRequest` API
- New default rules
- Remove support for INJECT_HTML_PLUGIN (obsolete)
- Remove support for INJECT_JS_CODE (unsupported by Manifest V3)
- Convert HTML snippets to Lit elements
- Add prettier config and reformat all files
- Bumped lit version to 3.1.0
## v0
#### v0.0.13/14
- Fix `content_scripts.matches` patterns
#### v0.0.12
- Restrict the extension to only work for Google hosted Gerrit
- Add documentation about testing and publishing the extension
#### v0.0.11
- Fix CORS preflight interception
- Update npm deps
- Make the extension look a bit nicer
#### v0.0.10
- Bumped lit version to 2.2.3
#### v0.0.9
- Move cors / cache override to rules, so user can disable it from the popup
- Change header value separator from `,` to `|`, as `,` can be part of the value while `|` is unlikely
- Fix `onGerritReady` to use tag name instead of id and max at 5s ;)
#### v0.0.8
- **BREAKING CHNAGE**: Gerrit is moving to `gr-app.js` only, so `gr-app.html` will no longer exists, we have updated default rules to forward to `gr-app.js` as well, in case you are still using `gr-app.html`, please modify that redirect rule by changing `gr-app.js` to `gr-app.html`
- Add `addRespHeader` operator, thanks to Edward
- Add `injectExp` operator, as gerrit now supports experiments, this is a quick way to force enabling certain experiments, experiments should be separated by `,`
#### v0.0.7
- Fix the issue when multiple rule matches one url for onBeforeRequest
- Block will always take the highest priority
- Then Redirect
- Ignore the rest
- Add a new operator as `injectJsModule`, with plugins moving to polymer 3, certain plugins will be written in modules, and to inject moduled js plugins, use this rule
- This will basically add a `type=\"module\"` to the script tag when load the script so we can use `import` inside
- With `type=\"module\"`, `document.currentScript` will become `null` so we won't be able to infer the plugin url, to workaround this, make sure you call `Gerrit.install` with the third parameter: `Gerrit.install(() => {}, undefined, 'the_url')` so Gerrit can treat it as a legit plugin
- Keep using `injectJsPlugin` if its a single bundled js file
#### v0.0.6
- Add two new operators:
- `addReqHeader` to add arbitrary header when you send a request
- `rRespHeader` to remove arbitrary header on any response
- Modify default rules to show # of js errors in the helper tip
- Add a new default rule to send x-test-origin with gerrit-fe-dev-helper on all requests when enabled
#### v0.0.5
- set crossorigin to anonymous to help debug js error from plugin
- improve the ui on popup
- remove outdated rule of replacing gr-app-p2 with gr-app
#### v0.0.4
- A better way to wait for Gerrit when injecting html plugins
#### v0.0.3
- Hotfix
#### v0.0.2
- Remove restriction on gerrit sites (some features won't work if its not a valid gerrit site)
- Update README
#### v0.0.1
- Enable the extension with a single click
- Allow export / import rules
- Show a error for 5s if rule destination is invalid (can not reach)
- Show an announcement for the change for 3 seconds for first time users
- Persist enable / disable state per tab
- Support temporary disable rule without deleting it
- Move injection to document_end
- Support reset to reset rules to initial state
- Support proxy live requests to local on googlesource sites
- Support 6 types of rules: redirect, block, injectJS code/url, inject html code / url
- Support add / remove / modify rules
Source Manifest.json
How to download and manually install Gerrit FE Dev Helper extension for Chrome
Looking for a way to install Gerrit FE Dev Helper extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.
However, you may need to install Gerrit FE Dev Helper extensions manually, this article outlines two simple methods to effortlessly install Gerrit FE Dev Helper extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.
Method 1: Download Gerrit FE Dev Helper extension and manually install through Drag &Drop
If you ever need to manually install a Gerrit FE Dev Helper extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.
Step 1: Download the Gerrit FE Dev Helper Extension by clicking the "Download CRX" button on the website.
Look for the Gerrit FE Dev Helper extension you wish to install. Go to the website and download the Gerrit FE Dev Helper extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for Gerrit FE Dev Helper extension that contains all the data.
Step 2: Extract &Arrange Files
Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.
Step 3: Go to the Chrome Extensions Page
Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.
Step 4: Drag and Drop the Extension
Now, go to the folder where you extracted the Gerrit FE Dev Helper extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.
Step 5: Complete the Installation
Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.
Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.
Method 2: Download Gerrit FE Dev Helper extension for Chrome and install in Developer Mode
This is another method to install Gerrit FE Dev Helper extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.
Step 1: Download the Gerrit FE Dev Helper extension file
Select and download the Gerrit FE Dev Helper extension by clicking the 'Download CRX' button on the website.
Step 2: Extract the downloaded contents
Convert the file to a ZIP file if it is in CRX format then extract the Gerrit FE Dev Helper extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your Gerrit FE Dev Helper extension running.
Step 3: Open Chrome Extension Setting Page
In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.
Step 4: Enable Developer Mode
After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.
Step 5: Load the Unpacked Extension
Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."
Step 6: Select the Extension Folder
Once the pop-up opens upon clicking Load unpacked, select the Gerrit FE Dev Helper extension directory and click on the "Select Folder "button.
Step 7: Confirm and Install
After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.
Conclusion
Here we've made a step-by-step guide on How to manually install Gerrit FE Dev Helper extension in 2 ways. We hope this guide proves helpful.
Similar Extensions
Dev Playground 364 2 ★ 288KiB
Recent Crbugs 364 2 ★ 488KiB
Highlight Me in Buildbot 364 1 ★ 38.77KiB
Flake linker 364 2 ★ 21.02KiB
Gerrit for Gmail 364 1 ★ 118KiB
Gerrit JIRA Link 364 4 ★ 321KiB
WikimediaDebug 364 3 ★ 145KiB

gist-more-url 364 1 ★ 61.76KiB
Hacker News Duplicate Detector 364 1 ★ 21.7KiB
Gerrit Plus - UI fixes for PolyGerrit UI 364 0 ★ 10.99KiB
Source Quicklinks 364 2 ★ 59.23KiB
Gerrit Monitor 364 6 ★ 41.11KiB
Chromite Butler 364 18 ★ 30.32KiB

Chromium Dev Refresh 364 0 ★ 13.22KiB
Atma.js DevTool 364 0 ★ 201KiB
LL Developer Tools 364 1 ★ 98.88KiB
Chrome OS Tree Status 364 2 ★ 68.71KiB
The-M-Project Inspector 364 4 ★ 12.79KiB
nShell 364 0 ★ 4.76MiB
Git Mining 364 4 ★ 211KiB
GitHub submodule links 364 2 ★ 17.49KiB
GitHub Enhancement Suite 364 1 ★ 56.24KiB
Lavaca Developer Tools 364 0 ★ 10.42MiB
User reviews
Nasser Grainawi (ID: 0000008765fd40da) Voted 5 ★ - Updated 11/14/2019
Paladox none (ID: 0000009b8bc15cb3) Voted 5 ★ - Updated 11/13/2019