A browser plugin to automatically sync cookies for local frontend development of GHN. This extension will copy cookies from portal and make them available for your development environment, including version sandbox deployments.
You can install the latest version of the Cookie Sync extension using the links below:
This is the recommended installation method.
You can download the bundled extension for your browser from the github releases page here.
NOTE: Auto-update will not work with manual installations.
-
- Visit:
chrome://extensions
oredge://extensions
orabout://extensions
(in opera). - Enable
Developer Mode
- Chrome/Opera: The toggle button is in the top-right corner
- Edge: The toggle button is in the left sidebar
- Refresh the page!
- Drag & drop the
.zip
file you downloaded into the page.
- Visit:
-
- Get an ESR, Developer, or Nightly build of firefox.
- Follow Mozilla's instructions to enable installing unsigned addons here.
- Visit
about:config
- Set
xpinstall.signatures.required = false
- Set
extensions.langpacks.signatures.required = false
- Visit
- Visit
about:addons
- Drag & drop the
firefox.xpi
file you downloaded into the page.
-
The full extension is not avaialble on Safari. Instead you can manually read cookies from the extension inside Firefox or a Chrome based browser then write those cookies into Safari.s
Using a browser with this extension installed:
- login to production and also the domain you want to use within Safari.
- for example, login to Portal Test or Portal Staging to get refreshed cookies
- Open the extension and click "Sync Cookies Now".
- Click the "Copy" button next to the domain you want to use within Safari.
- Paste the copied
document.cookie=...
snippet into the Safari JavaScript Console.
- login to production and also the domain you want to use within Safari.
Please file an issue here for feature requests, bugs, missing documentation, or unexpected behavior.
Ensure you have:
Then run the following:
yarn install
to install dependencies.yarn run dev:chrome
to start the development server for chrome extensionyarn run dev:firefox
to start the development server for firefox addonyarn run build:chrome
to build chrome extensionyarn run build:firefox
to build firefox addonyarn run build
builds and packs extensions all at once toextension/
directory
-
yarn install
to install dependencies. -
yarn run dev:chrome
oryarn run dev:firefox
To watch file changes in development -
Load the extension in your browser
NOTE: Remove any existing versions first
- Go to the browser address bar and type
chrome://extensions
. - Check the
Developer Mode
button to enable it. - Click on the
Load Unpacked Extension…
button. - Select the folder
cookie-sync/extension/chrome
.
Firefox ESR, Developer, or Nightly build
- Go to the browser address bar and type
about:debugging#/runtime/this-firefox
. - Click on the
Temporary Extensions
Section, then theLoad Unpacked Extension…
button. - Select the file
cookie-sync/extension/firefox.xpi
.
- Go to the browser address bar and type
yarn run build
builds the extension for all the browsers.
Note: By default the package.json
and manifest.json
are set with version 0.0.0
. The CI pipeline will set the version before building the bundles.
Update source/manifest.json
file with browser vendor prefixed manifest keys
{
"__chrome__name": "SuperChrome",
"__firefox__name": "SuperFox",
"__edge__name": "SuperEdge",
"__opera__name": "SuperOpera"
}
if the vendor is chrome
this compiles to:
{
"name": "SuperChrome",
}
Add keys to multiple vendors by separating them with | in the prefix
{
__chrome|opera__name: "SuperBlink"
}
if the vendor is chrome
or opera
, this compiles to:
{
"name": "SuperBlink"
}
See the original README of wext-manifest-loader
package for more details
Inspired by Sentry Cookie Sync