You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jqNote: This is not the jq on NPM, which is a server-side jQuery replacement.
The project is supplied with a Makefile which can produce final files for both Firefox and Chrome.
make chrome
make firefox
The build is done by selectively copying parts of the source code to the folder ./.tmp and then archiving it again using either zip (for Chrome) or web-ext (for Firefox).
The final archives are kept in the ./build folder.
For testing, the extension can be loaded into Chrome by going to chrome://extensions and clicking on the Load Unpacked Extension button.
Then navigate to the .tmp folder in the source code root which was created by running make chrome and load it. An alternate is to run make manifest in the root folder and then load the source code root as the unpacked extension. This will allow for a simpler edit-reload cycle, except while editing manifest.json.template.
For Firefox, the easiest way to test the packaged extension would be to download the unbranded build or the Developer Edition and loading the extension there. Otherwise, one would need to sign the extension via your account on their Addon server. Go to about:addons, to the Extensions Tab and click the Gear icon (Settings) on the top right to load the packed extension.
If the browser still complains that the package has not been signed, then go to about:config and set xpinstall.signatures.required to false. Note that this setting only takes effect on the Developer Edition and the Unbranded versions of the browser even though it shows up in about:config pages of the release channel versions as well.